Awesome-claude-plugins 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.

install

source · Clone the upstream repo

git clone https://github.com/ComposioHQ/awesome-claude-plugins

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/ComposioHQ/awesome-claude-plugins "$T" && mkdir -p ~/.claude/skills && cp -r "$T/perf/skills/benchmark" ~/.claude/skills/composiohq-awesome-claude-plugins-perf-benchmarker-d861b6 && rm -rf "$T"

manifest: perf/skills/benchmark/SKILL.md

source content

perf-benchmarker

Run sequential benchmarks with strict duration rules.

docs/perf-requirements.md

as the canonical contract.

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.