pnasnexus-submission
Use as the final preflight before submitting to PNAS Nexus — a complete checklist across fit, open access/APC/license, article type & length, Significance Statement, abstract, classification, figures, statistics, data/code, references, and required files. Covers the PNAS-transfer case and bundles a checklist and cover-letter template. Emits GO/NO-GO.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-submission --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.
# Submission Preflight (pnasnexus-submission) ## When to trigger - The manuscript is "done" and you're about to upload via the submission portal (pnasnexus.msubmit.net). - You want a single gate that confirms every other pnasnexus-* skill's output landed. - You are completing a **transfer from PNAS** and need to confirm nothing is missing. - A revision is going back and you need to confirm nothing
What does the pnasnexus-submission skill do?
Use as the final preflight before submitting to PNAS Nexus — a complete checklist across fit, open access/APC/license, article type & length, Significance Statement, abstract, classification, figures, statistics, data/code, references, and required files. Covers the PNAS-transfer case and bundles a checklist and cover-letter template. Emits GO/NO-GO.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pnasnexus-submission --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.