build-benchmarklisted
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:067ada6f8aa44d5b compiled from skills/build-benchmark/SKILL.md.spec.ts -->
# build-benchmark — the study + the artifact reviewers can run
## Run me
🔴 FIRST, before any other step:
```
node .claude/skills/paper-pipeline/scripts/announce.mjs build-benchmark <paper-dir>
```
An advisory pass cannot be observed failing — silence is both its error state and its normal
state — so starting is an event, and events get written down.
A measurement paper is only as strong as the artifact a reviewer can `cd` into and re-run. This skill
covers both halves: the study design that makes the finding true, and the self-checking artifact that
makes it *verifiable*. The contribution is the **method**, not the one tool you happened to test — build
so both survive review.
## 0. 🔴 READ THE STATED CLAIM FIRST — and refuse to design without it
**Before designing anything, open `<paper-dir>/PIPELINE-STATUS.md` and read row `frame`** — the one
paragraph saying what this paper will claim (written by `argument-arc` in **frame mode**, in SETUP).
🔴 **If `frame` is empty, stop. Do not design the study.** Go run `argument-arc` frame mode, get the
paragraph, then come back. This is a refusal, not a recommendation:
- **The frame decides which results matter.** A study designed without a stated claim measures
whatever the available harness can already see, and the claim gets fitted afterwards to whatever
came out. That is backwards, and it is expensive in exactly one directio