From pnas-skills
Writes a PNAS abstract: ~250 words, single paragraph, self-contained, quantified, accessible to broad scientific audience. Use after results/significance are settled.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pnas-skills:pnas-abstractThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Significance, track, structure, figures, stats, and data are settled (do this late).
Do not import a Science-style ≤125-word abstract or a one-sentence summary; PNAS abstracts are longer and there is no one-sentence summary. The short, plain artifact PNAS requires is the Significance Statement (
pnas-significance), which is separate.
| Abstract | Significance Statement (pnas-significance) |
|---|---|
| What/how/found, for scientists | Why it matters, for everyone |
| ~250 words, quantified, technical-but-clear | ≤120 words, plain language |
| Stands in for the paper | Stands in for the "so what" |
If the two read the same, the Significance Statement is wrong — fix it in pnas-significance.
【Abstract】 single paragraph (word count: N ≤ 250)
【Five moves present?】 context / gap / approach / quantified result / implication
【Quantified headline result?】 yes/no + the number
【Distinct from Significance Statement?】 yes/no
【Jargon hits removed】 [...]
【Next】 pnas-citation
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin pnas-skillsWrites PNAS Significance Statements — ≤120 words for a broad audience. Useful when drafting or revising the mandatory statement for PNAS submissions.
Polishes Science (AAAS) abstracts and one-sentence summaries: quantifies results, removes jargon, enforces ≤125 words. Use late-stage when format is settled.
Guides drafting or revising a scientific abstract using IMRAD structure. Ensures compliance with journal word limits and reporting standards.