Menu

Individual skill

benchmark-checklist

Seven evidence questions every performance number must pass before you report it or act on it. Use on /benchmark-checklist, whenever you produce a before/after timing, claim a speedup or regression, freeze a benchmark harness, or pick a library or setting for speed.

plugins/requie/endostack/skills/benchmark-checklist/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# benchmark-checklist

A timing number can mislead in seven common ways. Each question below catches one of them, and each answer must come from run data, not from reasoning about what probably happened. If you cannot answer a question, the verdict is inconclusive.

Use it any time you produce a speed number: before/after figures in a PR, a claimed improvement or regression, building or freezing a harness for an optimization loop, or choosing a library or setting on speed. Skip it for discussion that involves no measurement.

## Rough estimates

If the user asked only for a ballpark figure, one run is enough. You still answer question 4 (failures) and question 7 (work actually done), and you tell the user it was a single run. Skip the rest unless the number looks wrong. A comparison that feeds a decision is never a rough estimate.

## Before you measure

1. Write the sentence you want to publish, with the metric, the percentile, the size of the effect, and the dataset. For example: "p95 latency of `POST /search` drops from 41 ms to 28 ms on the 2 million row fixture." The seven questions test that sentence.
2. Read the harness. List what it times, what it counts, and what it leaves out.