Benchmark Checklist
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and...
Install
npx skills add cursor/plugins --skill benchmark-checklist -g -a claude-code -y- Repository
- cursor/plugins15k
- Category
- Engineering
- Updated
- 4d ago
- License
- See repository
- Context cost
- Lightabout 1,174 tokens
- Runs scripts
- No, instructions only
What it does
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
Benchmark checklist
Use this when you produce a performance number: a PR's before and after, a regression claim, a hillclimb harness, or a library or config choice. Answer each question with evidence from a run, not a guess about the code.
For a quick ballpark the user asked for, one run is enough. Still check questions 4 and 7, and say that it is one run. Skip the rest unless that run looks wrong. A choice between options is never a ballpark.
Before you run anything
- Write down the claim you expect to make, in the words you would ship ("export is 30% faster at p50 on the 60k-row dataset"). The questions test that sentence.
- Read the measurement script. Note what it times, counts, and ignores.
- Check the load average with
uptimeand the core count withnproc. If the machine is busy, find out what is running. If you cannot stop it, interleave the sides so both see the same noise, and say so in the report.
