Yuan1z0825/nature-skills / skills/nature-polishing
nature-polishing
VerifiedPolish, 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-mach-intell.md
View on GitHub# Journal: Nature Machine Intelligence — polishing
## Read the shared contract first
Open
`../../../../nature-shared/journal-formats/nature-machine-intelligence.md` for
the exact, stage-aware NMI facts. This fragment controls polishing decisions,
not the submission numbers themselves.
For Results or Discussion, also open
`../../../../nature-shared/core/nature-results-discussion.md`. It is
corpus-derived Nature-style writing guidance, not an official NMI requirement.
For Introduction polishing, also open
`../../../../nature-shared/core/nature-introduction.md`. It is corpus-derived
Nature-style writing guidance, not an official NMI requirement.
For abstract polishing, also open
`../../../../nature-shared/core/nature-abstract.md`. It is corpus-derived
Nature-style writing guidance, not an official NMI requirement.
## Audience and stance
Polish for readers across AI, robotics, machine learning and the scientific or
societal application domain. Preserve technical precision while making the
question, evidence and consequence understandable outside one specialist
benchmark community.
## Structure before sentence polish
For an Article, check these before line editing:
1. Count Introduction + Results + Discussion against the 3,500-word main-text
limit; exclude abstract, Methods, references and legends.
2. Keep the unreferenced abstract at or below 150 words.
3. Check that figures and tables total no more than six.
4. Keep the introduction unheaded; allow topical subheadings in Results and
Methods but not in Discussion.
5. Preserve enough Methods detail for replication; NMI does not publish a
fixed Methods word limit on the current pages.
Report an over-limit or wrong-structure manuscript under `Revision notes:`.
Do not silently delete evidence, uncertainty or reproducibility detail to make
the prose fit.
## Claim calibration
- Replace benchmark-only claims of general intelligence or deployment
readiness with the evaluated scope.
- Separate gains due to architecture from data, supervision, compute or tuning
differences.
- Name robustness and transfer boundaries when the prose currently hides them.
- Do not convert association, retrospective performance or simulation results
into causal, clinical or societal effectiveness.
- Define specialist abbreviations and remove jargon that is not needed for
technical accuracy.
## Results–Discussion calibration
- Preserve a claim-escalating Results sequence rather than flattening related
subsections into parallel experiment reports.
- Keep a bounded local inference in Results when it directly resolves the
current experiment; move cross-result synthesis and broader implications to
Discussion.
- Keep conclusion-changing robustness and failure boundaries visible in the
main text; move reassurance-only variants to SI.
- Permit a brief finding anchor in Discussion, but remove repeated evidence,
effect sizes, and tests that merely re-demonstrate the Results claim.
## Introduction calibration
- Compress broad context until the specific unresolved problem appears early.
- Replace vague limitation language with the exact unknown, condition,
mechanism, boundary, or literature tension.
- Reorganize citation catalogues into a known–unknown argument.
- Replace novelty adjectives with the research question and the design that can
answer it.
- Check that each Introduction question maps to a Results answer and that the
closing paragraph previews this route without replaying the paper.
## Abstract calibration
- Rebuild the abstract around one main discovery rather than a list of
datasets, models, metrics, and completed analyses.
- Keep only enough method information to show why the design answers the gap.
- Retain no more than one or two decisive supporting claims or boundaries.
- Keep a number only when it defines, supports, or bounds the main discovery.
- Make the final sentence state the bounded conceptual or field-level payoff,
not merely superior performance.
## Submission-sensitive checks
- Preserve explicit disclosure of a substantially extended conference paper.
- Preserve Data Availability and the separate Code availability section.
- Flag missing reviewer access or a missing Software Submission Checklist when
new code is central to the conclusions.
- Do not apply a flagship Nature title, Methods or legend limit. NMI's current
public pages state no current fixed number for those items. For figure
legends, use the official 2018 NMI below-300-word instruction only as a
historical advisory ceiling: count the complete legend, not each panel, aim
for 150–250 English words, and obey any newer editor or submission-system
instruction.
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 |