Yuan1z0825/nature-skills / skills/nature-writing
nature-writing
VerifiedDraft or restructure scientific manuscript arguments, sections, and initial-submission materials from author-provided evidence. Use for 论文写作、章节起草、论证重构、正文压缩、首次投稿材料. Use nature-polishing for language-only edits to existing prose and nature-response for post-decision correspondence.
static/fragments/journal/nat-comms.md
View on GitHub# Journal: Nature Communications (writing)
## Read the shared facts first
Open `../../../../nature-shared/journal-formats/nat-comms.md` for the authoritative formatting facts: word limits, abstract rules, figure specs, reference style, mandatory statements, and common desk-rejection patterns.
The notes below are the **drafting action layer** on top of those facts.
## Audience
Open-access, broader than a subfield journal, more specialist-tolerant than *Nature*. The reader is typically an active researcher in an adjacent area.
## Drafting priorities
- Significance framing matters, but a less aggressive opening than *Nature* is acceptable.
- Tight prose is still preferred even though limits are looser than *Nature*.
- Methods can be more detailed in-line; reproducibility expectations are explicit.
- Same em-dash and hedging defaults as *Nature*.
## Pre-drafting word budget (Articles)
The ~5,000-word cap **includes Methods**. For a new manuscript or substantial restructuring, reuse an established word budget or propose one as a working assumption. Ask only if it conflicts with the requested scope or an explicit author constraint; do not require budget approval for a local section edit:
| Section | Suggested budget |
|---|---|
| Introduction | ~700 |
| Results | ~2,000 |
| Discussion | ~800 |
| Methods | ~1,500 |
| **Total** | **~5,000** |
Adjust based on paper type:
- Methods-heavy paper → shift toward `~1,200 / 1,800 / 700 / 1,800` (Intro / Results / Disc / Methods)
- Bio/clinical with rich Results → shift toward `~600 / 2,400 / 800 / 1,200`
If the user already has prose, estimate the current split first; if Methods runs >1,800, name it as a budget risk before drafting more.
## Mandatory companion artifacts to plan early
Nature Communications enforces these at production. Mention them at the **planning** stage, not after drafting:
- Data Availability statement with **valid, public accession numbers** (not pre-publication holds)
- Code Availability statement if any custom code is used (Zenodo DOI or equivalent)
- Reporting Summary — fill with the same rigor as the manuscript itself; reviewers see it
- Cover letter (separate upload) — three sentences: what / what's new / why cross-disciplinary
## Display-item planning
- 10-item cap (figures + tables combined)
- **No Extended Data tier** — anything beyond 10 goes to Supplementary Information
- Decide upfront which results justify a main figure vs. Supplementary. Reviewers tolerate fewer main figures more easily than they tolerate overcrowded ones.
## Abstract drafting
- 150 words, unstructured single paragraph, no citations
- Spell out abbreviations at first use
- Lead with the finding, not the background — editors triage on the abstract
- Include quantitative results where possible
## Cross-skill notes
If the user is transferring from a *Nature* draft, the most common rework is:
1. Reabsorb the separate Methods block into the main text word budget
2. Redistribute figures beyond 6 (Nature limit) up to the 10-item cap or into Supplementary
3. Re-tune the opening for a slightly less aggressive significance framing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |