Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From perf
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 claudepluginhub agent-sh/perf --plugin perfHow 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.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
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