nature-response

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 always_load:

• 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.

Use references/intake-and-routing.md to fix the task mode, minimum inputs, and readiness state before drafting. Route appeal-like cases separately; do not draft an appeal as the default path.

3. Run the workflow

Follow the workflow in core/workflow.md: if the user pasted a journal email, first parse manuscript metadata, decision type, editor instructions, reviewer reports, required files, and deadlines from the email; identify mode and decision type; extract editor instructions (IDs E.1) then reviewer comments (R1.1, R2.1) when present; classify each item by response action and independently verified work status; build a strategy summary; draft point-by-point responses and/or a revision cover letter; map every claimed change to a manuscript location or explicit placeholder; mark changed manuscript text in red on a backed-up copy when editing; format quoted revised manuscript text in the response letter in italics; start each new reviewer response on a new page in LaTeX/print-oriented outputs; flag missing author input; run QA; and derive package readiness from the per-item statuses and blocking state.

Never invent experiments, citations, line numbers, figure panels, supplementary items, editor instructions, or manuscript changes. Mark anything the author must supply as AUTHOR_INPUT_NEEDED.

4. Reach for references only when needed

The files under references/ and templates/ are deep resources, not defaults. Open them on demand per the references.on_demand table in the manifest — for example references/comment-taxonomy.md to classify comments, references/action-mapping.md for tracker fields, references/tone-and-stance.md for disagreement wording, references/difficult-cases.md for impossible experiments / conflicting reviewers / appeal-like cases, references/chinese-author-alignment.md for Chinese author notes, references/latex-templates.md for .tex cover/response/redline outputs, and references/qa-checklist.md before finalizing.

Why this split

• The static layer is versioned and reviewable; the core stays small for a normal response.
• The dynamic layer keeps each invocation cheap: the difficult-case, taxonomy, and QA depth load only when a step needs them.
• The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
• This structure mirrors nature-writing, nature-polishing, nature-reader, nature-paper2ppt, nature-figure, and nature-citation.

---

nature-response 技能

English

nature-response 用于起草、审查和修改返修通信材料，包括逐点 reviewer response、revision cover letter、标红修改稿摘录和可编辑 LaTeX 模板。

适合用它做什么

• 解析编辑部决定信、返修邮件和 reviewer reports。
• 将意见拆成稳定编号，例如 E.1、R1.1、R2.3。
• 为每条意见制定回应策略、手稿修改动作和证据需求。
• 分开记录“采用什么回应动作”“任务做到哪一步”“整个回复包能否提交”，并要求完成状态有可核验材料。
• 起草正式、克制、可提交的英文逐点回复和 cover letter。
• 审查 rebuttal 草稿中的遗漏回复、防御性语气、无支撑声称和行号缺口。

典型请求

• “这是编辑邮件和审稿意见，帮我生成逐点回复框架。”
• “把我的中文修改说明改成英文 reviewer response。”
• “检查这份 rebuttal 是否漏回、语气是否太强、有没有缺证据。”

你需要提供

• 编辑决定信、审稿意见、返修要求或已有 rebuttal 草稿。
• 已完成或计划完成的实验、分析、图表、行号和手稿修改位置。
• 目标期刊、稿件号、题名和提交材料要求。

产出

• Response strategy summary。
• 逐点回复信、返修 cover letter 或 LaTeX response package。
• 手稿修改清单、缺失信息清单和风险提示。
• 带任务状态、所需输入、预期产物和是否阻塞最终提交的逐条 tracker。
• 可选标红修改稿摘录；原文修改必须基于作者提供的文本。

边界

• 不会编造实验、分析、行号、图版、统计结果或编辑要求。
• 对需要作者确认的信息会用中文标记，而不是直接写成事实。
• 如果任务是模拟投稿前审稿意见，优先使用 nature-reviewer。

相关技能

• nature-reviewer：投稿前模拟审稿人意见。
• nature-polishing：回复信和 cover letter 的英文语气打磨。
• nature-statistics：处理统计相关审稿意见。
• nature-ref-verifier：核查参考文献错误类意见。