$npx -y skills add Boom5426/Nature-Paper-Skills --skill nature-portfolio-playbookUse when choosing among Nature, Nature Methods, or Nature Biotechnology, or when preparing a Nature Portfolio life-science manuscript for venue fit, article-type framing, and policy-aware pre-submission checks.
| 1 | # Nature Portfolio Playbook |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Use this skill when the venue decision itself is still live, or when a manuscript already targets `Nature`, `Nature Methods`, or `Nature Biotechnology` and needs venue-specific framing before a heavy revision pass. |
| 6 | |
| 7 | This skill is about fit and policy. It does not replace `scientific-writing`, `manuscript-optimizer`, or `submission-audit`. |
| 8 | |
| 9 | ## When To Use |
| 10 | |
| 11 | Use this skill when: |
| 12 | - the user asks whether a story fits `Nature`, `Nature Methods`, or `Nature Biotechnology` |
| 13 | - the paper has a `Nature`-style tone but the actual venue is undecided |
| 14 | - the contribution could be framed as an `Article`, `Resource`, `Analysis`, or short-format methods report |
| 15 | - a manuscript is close to submission and needs a Nature Portfolio-specific preflight |
| 16 | |
| 17 | Do not use this skill when: |
| 18 | - the task is generic sentence-level editing |
| 19 | - the venue is a conference or a non-Nature journal |
| 20 | - the manuscript structure itself is still unstable and needs `manuscript-optimizer` first |
| 21 | |
| 22 | ## Venue Routing |
| 23 | |
| 24 | ### Flagship `Nature` |
| 25 | |
| 26 | Default to `Nature` only when the paper makes a broad conceptual advance that matters outside the immediate specialty and can be explained to non-specialists without heavy field-specific scaffolding. |
| 27 | |
| 28 | Use these framing defaults: |
| 29 | - prioritize broad readership over specialist density |
| 30 | - keep title and abstract low-jargon |
| 31 | - preserve the non-specialist-friendly summary paragraph expectation |
| 32 | - if fit is uncertain, explicitly test whether the broad-readership case is real before optimizing prose too far |
| 33 | |
| 34 | ### `Nature Methods` |
| 35 | |
| 36 | Prefer `Nature Methods` when the central contribution is a method, assay, platform, computational approach, or resource whose main claim is enabling power. |
| 37 | |
| 38 | Before calling a story `Nature Methods`-fit, check that the manuscript can support all of these: |
| 39 | - a clear technical advance over available approaches |
| 40 | - validation and benchmarking against credible baselines or alternatives |
| 41 | - enough detail or protocol access for reproducibility |
| 42 | - demonstrated general utility, not just one narrow showcase |
| 43 | - a compelling biological or biomedical application that shows why the method matters |
| 44 | |
| 45 | ### `Nature Biotechnology` |
| 46 | |
| 47 | Prefer `Nature Biotechnology` when the paper's value is not just technical novelty but biotechnology significance: enabling capability, translational relevance, engineering depth, platform utility, or community-scale resource value. |
| 48 | |
| 49 | Before calling a story `Nature Biotechnology`-fit, check that the manuscript can make legible: |
| 50 | - why the advance matters for biotechnology or medicine, not just for one specialist benchmark |
| 51 | - why the story is substantial enough for a full article rather than a narrower methods report |
| 52 | - whether the paper is truly an `Article` or would be better framed as a `Resource` |
| 53 | |
| 54 | ## Article-Type Check |
| 55 | |
| 56 | Do this early. Do not treat article type as formatting cleanup. |
| 57 | |
| 58 | - `Article`: full research story with multiple linked claims and a substantial evidence chain |
| 59 | - `Resource`: community-useful dataset, platform, atlas, database, or screening asset whose lasting value is broad reuse |
| 60 | - `Analysis`: integrative or comparative analytical study when the core contribution is the analytical insight rather than a new experimental method |
| 61 | - short-format method/report categories: use only when the story is tighter, more self-contained, and the journal explicitly supports that format |
| 62 | |
| 63 | If the manuscript keeps oscillating between `method paper` and `resource paper`, resolve that before rewriting the abstract or Results. |
| 64 | |
| 65 | ## Nature Portfolio Preflight |
| 66 | |
| 67 | Run this before calling a draft submission-ready: |
| 68 | |
| 69 | 1. Reporting standards |
| 70 | - confirm whether a reporting summary will be required |
| 71 | - make sure the manuscript and supplement already contain the information that summary will demand |
| 72 | 2. Data and code availability |
| 73 | - check that repository names, accession IDs, download links, and access restrictions are ready to disclose |
| 74 | - do not wait until after acceptance to figure out the data/code statement |
| 75 | 3. Protocol and reproducibility readiness |
| 76 | - for methods papers, ensure the usable protocol path is clear: supplement, protocol repository, or public method record |
| 77 | 4. Image integrity and raw data |
| 78 | - ensure unprocessed source images and raw blot/gel material can be produced if requested |
| 79 | - remove any figure-preparation habit that could look like selective enhancement |
| 80 | 5. AI and attribution |
| 81 | - disclose qualifying use of generative AI tools where the journal requires it |
| 82 | - do not treat AI-made images or undisclosed AI-written content as safe by default |
| 83 | 6. Related-manuscript and preprint disclosures |
| 84 | - disclose preprints, overlapping submissions, related manuscripts, and conference-proceedings history when relevant |
| 85 | |
| 86 | ## Wo |