Agent skill · writing content · yuan1z0825
nature-response
Draft, audit, or revise Nature-style revision correspondence packages: point-by-point reviewer-separated response letters, rebuttal letters, revision cover letters, LaTeX cover/response templates, and red-marked revised-manuscript excerpts. Keep mutually blind reviewers isolated so no reviewer-facing response reveals another reviewer's comments, numbering, recommendation, or author response. Prevent reviewer-driven manuscript accretion by preferring replacement, compression, or SI relocation over appending non-central defense prose. Use for reviewer comments, editor decision letters, pasted editorial emails, response drafts, cover letters, response to reviewers, rebuttal, 修回信, 返修邮件, 编辑邮件, 返修 cover letter, 审稿意见回复, 逐点回复, 大修回复, 小修回复, 回复审稿人, 修改稿回复, 写rebuttal, 回应审稿意见, 标红修改, or LaTeX 模板.
Why this skill is useful
Adds a structured workflow and templates for drafting complex Nature-style revision correspondence that the AI cannot generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 33,818 stars on the source repository.
What this skill does
Nature Reviewer Response — Router This skill is split into two layers: A static layer under static/ that holds versioned, reusable content fragments (the default stance and red lines, and the response workflow with output format). A dynamic layer (this file plus manifest.yaml) that loads the core every time and reaches for the deeper response references or templates only when a step needs them. Do not try to apply the response logic from memory or from this router. Always load fragments from disk as described below. Routing protocol Follow these four steps every time the skill is invoked. 1. Load the manifest and the core layer Read manifest.yaml. Then read every file listed under alwaysload: static/core/stance.md — the editor-facing purpose, the default stance, the red lines, and the source hierarchy that apply to every response job. static/core/workflow.md — accepted inputs, the revision correspondence workflow, and the output package format. 2. No content axis — identify mode and language inline Unlike nature-writing or nature-figure, nature-response has no fragment axis. Its variation is identified at runtime, not by loading different content bodies: task mode — draft / audit / revise / triage-only / cover-letter / revision-package / latex-template / appeal-like. decision type — minor revision, major revision, revise-and-resubmit, transfer after review, or unclear. user language — if the user writes Chinese, also produce the 中文核对 block. Decision type is a required intake gate for normal revision work. First extract it from an editor decision letter when available. If it is still unclear, ask the user whether this is a Major Revision or Minor Revision before drafting a response strategy or response prose. Do not infer the decision from the number, tone, or apparent difficulty of reviewer comments. Use references/intake-and-routing.md to fix the task mode, minimum inputs, and readiness state before drafting. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yuan1z0825/nature-response