$npx -y skills add Boom5426/Nature-Paper-Skills --skill paper-workflowUse when deciding which paper-related skill to use or how to sequence manuscript work from project setup through submission and rebuttal.
| 1 | # Paper Workflow |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Use this skill as the routing map for paper work. It does not replace the specialized skills. It tells you which one to use next. |
| 6 | |
| 7 | Default assumption: unless the user explicitly names a conference venue, the manuscript should follow the journal-oriented, `Nature`-style workflow. |
| 8 | |
| 9 | When writing follows experiments or analysis performed across multiple sessions, freeze a compact handoff first: current paper story, supported findings, unresolved decisions, and the figure list that actually carries those findings. |
| 10 | |
| 11 | ## Routing Map |
| 12 | |
| 13 | Use: |
| 14 | - `paper-bootstrap` when a project is new, messy, or missing a source of truth |
| 15 | - `nature-portfolio-playbook` when the target is `Nature`, `Nature Methods`, `Nature Biotechnology`, or the venue fit among those journals is still unclear |
| 16 | - `scientific-writing` when drafting or rewriting sections in prose |
| 17 | - `manuscript-optimizer` when the paper's claim structure, evidence chain, terminology, or prose need revision |
| 18 | - `results-section-revision` when the Results section is scientifically stable but the subsection flow, paragraph openings, or argument progression still feel jumpy |
| 19 | - `figure-planner` when the main bottleneck is figure logic, panel roles, or legend sync |
| 20 | - `citation-verifier` when bibliography hygiene or source verification is the bottleneck |
| 21 | - `data-availability` when repository plans, accession numbers, source-data coverage, or Data Availability wording are the bottleneck |
| 22 | - `submission-audit` when the paper is near submission or resubmission and needs a preflight pass |
| 23 | - `rebuttal-response` when reviewer comments exist and a response letter plus aligned manuscript edits are needed |
| 24 | - `conference-paper-writing` only when the user explicitly wants a conference paper for venues such as NeurIPS, ICML, ICLR, ACL, AAAI, or COLM |
| 25 | |
| 26 | ## Default Sequence |
| 27 | |
| 28 | For most journal manuscripts, prefer this order: |
| 29 | |
| 30 | 1. `paper-bootstrap` |
| 31 | 2. `nature-portfolio-playbook` when venue fit or article type is uncertain |
| 32 | 3. Refresh `notes/project_truth.md`, `notes/result_summary.md`, and `notes/paper_handoff.md` after any major experimental or figure update |
| 33 | 4. `scientific-writing` or `manuscript-optimizer` |
| 34 | 5. `figure-planner` |
| 35 | 6. `results-section-revision` when Results is substantively right but narratively abrupt |
| 36 | 7. `citation-verifier` |
| 37 | 8. `data-availability` |
| 38 | 9. `submission-audit` |
| 39 | 10. `rebuttal-response` after external review |
| 40 | |
| 41 | ## Common Mistakes |
| 42 | |
| 43 | - using conference-style writing skills by default for journal manuscripts |
| 44 | - polishing sections before the active manuscript source of truth is clear |
| 45 | - rewriting the manuscript from experiment memory instead of a current `result_summary.md` or `paper_handoff.md` |
| 46 | - editing figure legends late without rechecking the Results text |
| 47 | - leaving repository choice, accession IDs, or source-data coverage until the submission portal is already open |
| 48 | - postponing Nature Portfolio article-type or venue-fit decisions until after the paper is mostly rewritten |
| 49 | - treating citation formatting as the same thing as citation verification |
| 50 | - writing a response letter before deciding the underlying manuscript edits |