From perf
Enforces sequential performance benchmarks with 60s min duration (30s binary search), 10s warmup, anomaly re-runs, and JSON metrics output for baselines/regressions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/perf:perf-benchmarker [command] [duration][command] [duration]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run sequential benchmarks with strict duration rules.
Run sequential benchmarks with strict duration rules.
Follow docs/perf-requirements.md as the canonical contract.
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);
command: <benchmark command>
duration: <seconds>
warmup: <seconds>
results: <metrics summary>
notes: <anomalies or reruns>
Benchmarks MUST emit a JSON metrics block between markers:
PERF_METRICS_START
{"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}}
PERF_METRICS_END
npx claudepluginhub agent-sh/perf --plugin perfUse when a backpressured loop needs to run benchmarks on a performance-sensitive project and decide whether a change is a regression, an improvement, or a wash — per-iteration sanity checks and the full pre-done run.
Guides using Bencher continuous benchmarking to track performance, detect regressions, set up CI checks, and run benchmarks.
Creates performance baselines for load testing and benchmarking. Provides step-by-step guidance and generates configurations for baseline metrics.