PNAS Skills
by @brycewang-stanford · plugin · 9 skills
Twelve-skill bundle covering the PNAS manuscript lifecycle: workflow router, scope/significance fit, submission-track selection (Direct vs Contributed), the ≤120-word Significance Statement, ≤250-word abstract, main-text writing with in-text Materials and Methods + classification, display items, statistics & reproducibility, data/code availability, numbered reference style, submission preflight, a
Install the whole plugin (CLI)
npx skillmds add brycewang-stanford/pnas-fit
npx skillmds add brycewang-stanford/pnas-data
npx skillmds add brycewang-stanford/pnas-track
npx skillmds add brycewang-stanford/pnas-figures
npx skillmds add brycewang-stanford/pnas-writing
npx skillmds add brycewang-stanford/pnas-abstract
npx skillmds add brycewang-stanford/pnas-citation
npx skillmds add brycewang-stanford/pnas-rebuttal
npx skillmds add brycewang-stanford/pnas-workflowSkills in this plugin
- ▌ pnas-fit · brycewang-stanfordUse before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.
- ▌ pnas-data · brycewang-stanfordUse to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.
- ▌ pnas-track · brycewang-stanfordUse to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.
- ▌ pnas-figures · brycewang-stanfordUse to finalize PNAS display items — column-width sizing (~9 / 11.4 / 18 cm), minimum font sizes, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, image integrity, and color-mode notes. Enforces figure rigor before submission.
- ▌ pnas-writing · brycewang-stanfordUse to structure a PNAS main text and hold its length — Title, Significance Statement, Abstract, Introduction, Results, Discussion, in-text Materials and Methods, references — and to choose the required Classification (Biological/Physical/Social Sciences + minor subject) and keywords at submission.
- ▌ pnas-abstract · brycewang-stanfordUse 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.
- ▌ pnas-citation · brycewang-stanfordUse to convert references to PNAS's numbered citation style — cited in order of appearance, a numbered reference list, full author lists, abbreviated journal titles. Provides formats for article/book/chapter/dataset/preprint and an author-date → PNAS conversion table. Late-stage style pass.
- ▌ pnas-rebuttal · brycewang-stanfordUse after PNAS reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Do not run before the main text is actually revised.
- ▌ pnas-workflow · brycewang-stanfordUse when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.