← ClaudeAtlas

argument-arclisted

Build or repair the paper's argument architecture — the one-sentence-per-section outline, the bottom-up inevitability pass, and the name/number budget. Run it when the reader says the paper throws ideas at them, when a structural objection repeats, or before any large rewrite. Not a prose or length skill.
zernie/paperlint · ★ 7 · AI & Automation · score 74
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:05a1eaa79bb596d5 compiled from skills/argument-arc/SKILL.md.spec.ts --> # argument-arc — does the paper carry the reader to one conclusion > **Which structure skill?** `tighten-paper` = length, sag, what to cut. `grade-paper-writing` = > sentences, jargon, where a reader stalls. **`argument-arc` (you are here) = the load-bearing order > of ideas.** The first two assume the argument is right and the delivery is wrong. This one asks > whether the argument exists. Run it *before* them — cutting words inside a broken arc is how a > session burns a day and ships the same paper. ## Run me 🔴 FIRST, before any other step: ``` node .claude/skills/paper-pipeline/scripts/announce.mjs argument-arc <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 failure it exists to catch has a signature: every paragraph is defensible, every number is real, and the reader still finishes the section unable to say what it was for. That is not a prose problem and no amount of rewriting sentences fixes it. ## Two modes — and one of them runs BEFORE the study exists | Mode | Where it runs | Scorecard row | What it produces | |---|---|---|---| | **frame** | SETUP, before any run | **`frame`** | **One paragraph: what will this paper claim, and what would have to be true for that claim to hold?** | | **rebuild** | the LOOP, on a draft whose framing is wrong |