Perf Benchmarker
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-benchmarker is a skill that runs sequential performance benchmarks with strict duration rules to establish baselines and validate regressions.
About
This skill runs sequential performance benchmarks under strict duration rules to establish baselines and validate regressions. A developer uses it when they need reliable, non-parallel benchmark measurements. It enforces a 60 second minimum run, a 10 second warmup, re-running of anomalies, and emits metrics as a JSON block between markers.
- Runs sequential performance benchmarks with strict duration rules
- Enforces a 60s minimum run (30s only for binary search) and 10s warmup
- Emits a JSON metrics block between PERF_METRICS markers
Perf Benchmarker by the numbers
- 2 all-time installs (skills.sh)
- Ranked #464 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-benchmarker capabilities & compatibility
- Capabilities
- benchmarking · regression detection · baseline management
- Use cases
- testing · debugging
What perf-benchmarker says it does
Benchmarks MUST run sequentially (never parallel).
Minimum duration: 60s per run (30s only for binary search).
Do not change code while benchmarking.
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-benchmarkerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Run sequential performance benchmarks with a 60s minimum and 10s warmup to establish baselines or validate regressions.
Who is it for?
Developers who need statistically sound benchmark runs that avoid parallel-execution noise.
Skip if: Quick, casual timing checks or profiling of specific hot paths.
When should I use this skill?
You are running performance benchmarks, establishing baselines, or validating regressions with sequential runs.
What you get
Reliable sequential benchmark metrics emitted as a structured JSON block for downstream analysis.
- benchmark metrics JSON
- warmup and run summary
By the numbers
- 60s minimum run duration
- 10s minimum warmup
- 30s runs only for binary search
Files
perf-benchmarker
Run sequential benchmarks with strict duration rules.
Follow docs/perf-requirements.md as the canonical contract.
Parse Arguments
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const command = args.find(a => !a.match(/^\d+$/)) || '';
const duration = parseInt(args.find(a => a.match(/^\d+$/)) || '60', 10);Required Rules
- Benchmarks MUST run sequentially (never parallel).
- Minimum duration: 60s per run (30s only for binary search).
- Warmup: 10s minimum before measurement.
- Re-run anomalies.
Output Format
command: <benchmark command>
duration: <seconds>
warmup: <seconds>
results: <metrics summary>
notes: <anomalies or reruns>Output Contract
Benchmarks MUST emit a JSON metrics block between markers:
PERF_METRICS_START
{"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}}
PERF_METRICS_ENDConstraints
- No short runs unless binary-search phase.
- Do not change code while benchmarking.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
Can benchmarks run in parallel?
No, the skill requires benchmarks to run sequentially and never in parallel.
What is the minimum run duration?
60 seconds per run, with 30 seconds allowed only during the binary-search phase, plus a 10 second warmup.