perf-benchmarker
Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
npx skills add agent-sh/agentsys --skill perf-benchmarker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# perf-benchmarker Run sequential benchmarks with strict duration rules. Follow `docs/perf-requirements.md` as the canonical contract. ## Parse Arguments ```javascript 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_END ``` ## Constraints - No short runs unless binary-search phase. - Do not change code while benchmarking.
- Parse Arguments
- Required Rules
- Output Format
- Output Contract
- Constraints
What does the perf-benchmarker skill do?
Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill perf-benchmarker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agent-sh/agentsys, a repository with 923 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.