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/core/output-format.md
View on GitHub# Output format (writing)
Default output:
1. `Draft:` — the requested prose.
2. `Section outline:` — `3-7` compact bullets when the task involves a full section.
3. `Assumptions or missing inputs:` — only material issues; do not pad with style nits.
4. `Claim-evidence map:` — for major claims, in the form:
`Claim: ... | Evidence: ... | Status: supported / needs evidence / inferred`
5. `Why this structure:` — `2-4` short bullets on the structural choices made.
6. `To redirect me:` — one line inviting targeted feedback, e.g. "Name the paragraph or claim that is off and I will revise only that, keeping the rest." This sets up the targeted revision loop (workflow step 9) instead of a full rewrite.
For Chinese-author notes, provide polished English first, then brief Chinese notes explaining major structural choices.
For a Results or full-main-text restructuring task, also include a compact
`Main-text discipline audit:` after the prose:
- result allocation: core / necessary support / qualification / SI-bound detail
- relocated, replaced, compressed, or deleted material
- primary statistic retained in the main text and secondary analyses routed to SI
- before/after word count for each revised subsection
Return the full allocation and claim-repetition tables only when the manuscript
is being comprehensively restructured or the user asks for the audit trail.
If essential evidence or boundary is missing, do not invent. Write a placeholder such as `[Evidence needed: comparator group accuracy on test set X]` and list it under `Assumptions or missing inputs:`.
For `task=submission-package`, replace the default manuscript format with:
1. `Submission readiness:`
2. `Deliverable matrix:`
3. `Draft materials:`
4. `AUTHOR_INPUT_NEEDED:`
5. `Cross-file consistency checks:`
6. `Next actions:`
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: 194k | 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: 194k | 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: 194k | Updated | Claude CodeCodex | Verified | Install |