pnas-abstract
Use to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnas-abstract --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Abstract (pnas-abstract) ## When to trigger - Significance, track, structure, figures, stats, and data are settled (do this late). - The abstract reads like a methods recap with no result. - The abstract is being confused with, or duplicated from, the Significance Statement. - The abstract is over ~250 words, structured with subheadings, or jargon-dense. ## The PNAS abstract: ~250 words, single paragraph, self-contained - **Length:** up to **~250 words** (confirm the exact cap in current PNAS author guidelines). - **One paragraph, no subheadings**, no reference citations, no figure/table callouts. - **Self-contained:** a reader who sees only the abstract should understand the question, what was done, what was found (quantified), and what it means. - **Accessible** to the broad PNAS readership across Biological/Physical/Social Sciences — define or avoid acronyms. > 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 vs Significance Statement (keep them distinct) |
- When to trigger
- The PNAS abstract: ~250 words, single paragraph, self-contained
- Abstract vs Significance Statement (keep them distinct)
- Recommended five-move structure (no labels in the text)
- Hard constraints
- Jargon blacklist (rewrite on sight)
- Before / after: opening a PNAS abstract for a general reader
- Referee-facing checklist for the abstract
- Output format
- Anti-patterns
What does the pnas-abstract skill do?
Use to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnas-abstract --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.