Individual skill

pnas-significance

Use to write the mandatory PNAS Significance Statement — ≤120 words, written so an educated reader outside the field (down to an undergraduate) understands why the work matters. Distinct from the abstract. The highest-value PNAS-specific artifact.

PNAS-Skills/skills/pnas-significance/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Significance Statement (pnas-significance)

## Why this is a flagship PNAS skill

Every PNAS research article must include a **Significance Statement** — a short, mandatory, separately submitted paragraph that explains, in plain language, **why the work matters to science and society**. It appears prominently with the article and is read by editors at triage and by the broad readership. It is **not** a second abstract. Getting it right is one of the highest-leverage things you can do for a PNAS submission, so draft it as soon as the central claim is locked — do not leave it to the final upload.

## When to trigger

- The submission has no Significance Statement.
- The Significance Statement just restates or condenses the abstract.
- It is dense with jargon and undefined acronyms.
- It exceeds ~120 words.

## The hard rule: ≤120 words, written for a non-specialist
Back to top