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/section/results.md
View on GitHub# Section: Results
Results are the evidence chain that establishes and advances the paper's
scientific claims.
Load `../../../../nature-shared/core/nature-results-discussion.md` when the
target is Nature / Nature Portfolio. Rebuild the section around a discovery
loop, a core-capability validation envelope, or a capability ladder rather than
an experiment inventory.
Results writing should:
- load `../../../../nature-shared/core/main-text-discipline.md` and classify
every result before deciding its location
- stay mainly in past tense
- report what was observed, under what conditions, and with what quantitative support
- use statistics correctly and sparingly
- keep core discovery and necessary support in the main text
- move non-central robustness, heterogeneity, provenance detail, alternative
inference, and edge cases to SI unless they change the conclusion
- report the main descriptive quantity and primary inferential support once;
avoid duplicating the full report in both Results and captions
End each coherent evidence unit with the bounded inference it supports. Keep
local interpretation when it directly answers the current experiment and the
supporting evidence is visible there; move cross-result synthesis, extensive
literature comparison, and broad implications to Discussion.
## Sentence syntax (Results vs Discussion)
Results sentences usually report:
- `was detected`
- `increased`
- `showed`
- `enabled`
- `achieved`
Use interpretive syntax (`may reflect`, `suggests that`, `is likely due to`)
only when the transition is intentional, evidence-bound, and calibrated.
## Common failure modes
- Adding an inline interpretation that is unsupported by the current evidence,
or expanding a bounded inference into broad Discussion.
- Citing supplementary data when the result should stand in the main text.
- Treating every completed analysis as main-text material.
- Appending reviewer-defense sentences without checking what they replace.
- Explaining why a secondary analysis does not contradict the main result over
several recursive sentences instead of moving the reconciliation to SI.
- Restating the same claim in a heading, transition, caption, Results paragraph,
and closing sentence without adding a new function.
- Vague comparisons (`higher than control`) without effect size or test.
- Replaying an earlier baseline or control and drawing the same conclusion in a
later subsection, instead of centring the new perturbation, falsification,
stronger comparator, or boundary that creates the deeper inference.
After restructuring, apply the paragraph necessity test to every Results
paragraph and record whether text was retained, compressed, relocated, or
deleted. Do not move contradictory or conclusion-changing evidence out of the
main text.
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 |