pnasnexus-significance
Use to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters. Required for Research Reports and Stage 2 Registered Reports. Distinct from the abstract. One of the highest-value PNAS Nexus front-matter artifacts.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-significance --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.
# Significance Statement (pnasnexus-significance) ## Why this is a flagship PNAS Nexus skill Every PNAS Nexus **Research Report** (and **Stage 2 Registered Report**) must include a **Significance Statement** — a short, mandatory paragraph that explains, in plain language, **why the work matters to science and society**. It is read by editors at triage and by the broad, cross-disciplinary readership. It is **not** a second abstract. Getting it right is one of the highest-leverage things you can do, so draft it as soon as the central claim is locked. ## When to trigger - The submission (Research Report / Stage 2 Registered Report) has no Significance Statement. - The Significance Statement just restates or condenses the abstract. - It is dense with jargon and undefined acronyms. - It is **shorter than 50 words** or **longer than 120 words**. ## The hard rule: 50–120 words, written for a broad audience - **Length:** **between 50 and 120 words.** PNAS Nexus states an explicit **minimum of 50** and **maximum of 120** words — so unlike a one-line summary, a too-short statement is also non-compliant. Confirm both bounds in the current PNAS Nexus author guidelines. - **Audience:** an **edu
- Why this is a flagship PNAS Nexus skill
- When to trigger
- The hard rule: 50–120 words, written for a broad audience
- What it must do (and not do)
- Template (a few short moves, no headings)
- Worked shape
- The non-specialist rewrite drill
- Common failures (rewrite on sight)
- Output format
- Anti-patterns
What does the pnasnexus-significance skill do?
Use to write the PNAS Nexus Significance Statement — between 50 and 120 words, in plain language for a broad scientific audience, explaining why the work matters. Required for Research Reports and Stage 2 Registered Reports. Distinct from the abstract. One of the highest-value PNAS Nexus front-matter artifacts.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-significance --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 909 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.