Skip to content

Yuan1z0825/nature-skills / skills/nature-polishing

nature-polishing

Verified

Polish, translate, or tighten existing academic prose while preserving facts, terminology, and evidence boundaries. Use for 论文润色、学术翻译、正文精简, or manuscript LaTeX layout fixes. Use nature-writing when the main task is drafting new sections or rebuilding the manuscript argument.

static/fragments/journal/nat-comms.md

View on GitHub
# Journal: Nature Communications (polishing)

## 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 **polishing action layer** on top of those facts.

## Audience

Open-access, broader than a subfield journal but more specialist-tolerant than Nature. The reader is typically an active researcher in an adjacent area.

## Polishing priorities

- Significance framing matters, but a less aggressive opening than Nature is acceptable.
- Word count is more forgiving than Nature, but **the ~5,000-word cap includes Methods**. If polishing brings the manuscript near the limit, surface a word-budget check rather than just compressing prose.
- Methods can stay more detailed in-line; do not strip reproducibility content just to hit length.
- Same em-dash and hedging defaults as Nature.
- Abstract is unstructured, 150 words, no citations. If the user's abstract has citations or is structured (Background/Methods/Results), restructure before sentence polishing.

## Length-aware polishing checks

When polishing a Nature Communications Article, run these word-budget checks before sentence-level work:

1. Estimate total word count **including Methods**. Verify the current journal limit when submission compliance is requested. If over the applicable limit, continue meaning-preserving polishing and flag the gap in Revision notes. Obtain approval before substantive cuts to results, methods, or argument; length diagnosis does not block language edits.
2. If display items > 10, flag for redistribution into Supplementary Information before deeper edits.
3. If references > ~60, flag for trimming or consolidation.
4. If the abstract is > 150 words or contains citations, restructure first.

These are diagnostic, not destructive — surface the problem in `Revision notes:` rather than silently cutting.

## Things the shared facts already cover

Do not restate facts that live in `nature-shared/journal-formats/nat-comms.md`. Reference them when the user asks. Examples Claude should respond by reading shared facts:

- "What's the reference style?" → cite the format example from shared
- "How many figures can I have?" → cite the 10-item cap from shared
- "What's the abstract limit?" → 150 words, unstructured, no citations
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall