From paper-writer
Argumentation template for constructing paper sections. Each claim must be paired with explicit evidence and an explicit narrative function. Loaded by outline-architect and draft-writer.
How this skill is triggered — by the user, by Claude, or both
Slash command
/paper-writer:claim-evidence-chainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill encodes the argumentative discipline used to build sections. The unit of paper structure is the **claim**, not the paragraph or section.
This skill encodes the argumentative discipline used to build sections. The unit of paper structure is the claim, not the paragraph or section.
Every claim in your outline / draft has THREE parts:
CLAIM: The proposition you assert.
EVIDENCE: The specific data / citation / equation that supports it.
FUNCTION: Why this claim is HERE, in THIS section, in THIS order.
A claim with no FUNCTION is decoration — delete it. A claim with no EVIDENCE is hand-waving — find evidence or delete it. A claim with no CLAIM (just data) is a result without an argument — make the assertion explicit.
For each claim, verify:
| Evidence Type | Can Support | Cannot Support |
|---|---|---|
| Single experiment | "X happened in this setting" | "X happens in general" |
| Ablation | "Component Y contributes to performance" | "Y is necessary in all settings" |
| Citation | "Prior work observed X" | "X is true" |
| Theoretical proof | "Under assumptions A, X holds" | "X holds in practice" |
| Visualization | Existence claims, qualitative trends | Quantitative magnitude |
| Statistical test | "Difference is unlikely under null" | "Effect is large/important" |
Use this table to check whether the EVIDENCE actually supports the CLAIM. Mismatches are the #1 source of reviewer attacks.
A claim's FUNCTION in the narrative is one of:
Every claim should fit cleanly into one. A claim that doesn't fit is probably either misplaced or split-able.
Mark claims that the entire paper depends on with [LOAD-BEARING]. Example:
"Our active-learning strategy outperforms random sampling on out-of-distribution tasks. [LOAD-BEARING]"
Load-bearing claims must:
A typical paper has 2-4 load-bearing claims. More than 6 means the argument is overloaded.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub nugkta/paper-writer --plugin paper-writer