← ClaudeAtlas

paper-statuslisted

Answer "what's the status of the paper?" in one pass — MEASURE what is measurable (page count from the real build, git state, which gates were run against the CURRENT text), then read the judgement rows, then print blockers worst-first split into mine and the author's. Use whenever the author asks "what's up with the paper / status / what's left / is it ready", at the start of a session touching a paper, or before deciding what to work on next. Not a review skill — it reports state, it does not grade, cut, or fix.
zernie/paperlint · ★ 7 · Code & Development · score 74
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:51bc50b2485782e4 compiled from skills/paper-status/SKILL.md.spec.ts --> # paper-status — state, measured before it is narrated ## Run me 🔴 FIRST, before any other step: ``` node .claude/skills/paper-pipeline/scripts/announce.mjs paper-status <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. The author asks "what's the status there?" constantly, and the answer keeps coming from the wrong place: my memory of the session, which drifts, or a 200-line scorecard he cannot skim. Both fail the same way — **they narrate state instead of measuring it.** Grounding failure, 2026-08-04 (`compile-rules-2026`, day before deadline): a status line in chat said the review panel was running. It had never been launched. Another said the paper was 8 pages while the real build said 9 and BLOCKED — steering a whole day of cuts by the wrong instrument. Both would have been caught by running two commands instead of recalling two facts. ## The rule this skill exists to enforce **Anything a command can answer is not allowed to come from memory or from prose.** Measure first, read the scorecard second, and mark clearly which is which. A claim in `PIPELINE-STATUS.md` is a claim about the past; the build is the present. ## 🔴 The second rule: status is PUSHED, never waited for The corpus owner, 2026-08-05: *"I have to constantly ask for the paper's status