Draft, audit, or revise point-by-point reviewer response letters for Nature-family manuscript revisions. Use when the user provides reviewer comments, editor decision letters, revision notes, response drafts, or asks how to respond to major/minor revision requests, rebuttal letters, response to reviewers, peer-review reports, 审稿意见回复, 逐点回复, 修回信, 大修回复, 小修回复, or 如何回复 reviewer.
79
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Use this skill to convert editor decision letters, reviewer comments, author notes, or draft rebuttals into an auditable point-by-point response package for manuscript revisions.
The response letter is an editor-facing verification document. The goal is to show that every reviewer concern has been understood, addressed, and mapped to a concrete manuscript change, justified scientific response, or unresolved author action.
AUTHOR_INPUT_NEEDED.The skill may receive:
If reviewer boundaries or comment segmentation are ambiguous, flag the ambiguity instead of inventing reviewer structure.
draft, audit, revise, triage-only, or appeal-like.E.1, then split reviewer comments with IDs such as R1.1, R1.2, and R2.1.triage-only or appeal-like.ready_to_submit, draft_with_placeholders, needs_author_input, or blocked.Unless the user asks for another format, return:
Response strategy summary
- Decision type:
- Overall posture:
- Major risks:
- Suggested ordering:
Comment-response tracker
| ID | Reviewer concern | Type | Severity | Proposed action | Missing author input |
|---|---|---|---|---|---|
Draft point-by-point response letter
[editor-readable English response]
Manuscript change checklist
- [specific manuscript changes or placeholders]
Missing information / risk flags
- [specific unresolved items or "None"]
中文核对
- [when the user writes in Chinese; otherwise omit unless useful]| File | Open when |
|---|---|
| references/intake-and-routing.md | Before drafting, to identify task mode, minimum inputs, editor IDs, readiness state, and clarifying-question need |
| references/source-basis.md | You need source hierarchy, rule provenance, or policy-vs-advice boundaries |
| references/response-structure.md | You need the response package format or point-by-point letter anatomy |
| references/comment-taxonomy.md | You need to classify reviewer comments by category and severity |
| references/action-mapping.md | You need action labels, tracker fields, and missing-input states |
| references/tone-and-stance.md | You need recommended language, forbidden phrasing, or disagreement tone |
| references/chinese-author-alignment.md | The user writes in Chinese or provides Chinese author notes |
| references/difficult-cases.md | The comments involve impossible experiments, factual errors, conflicting reviewers, citations, statistics, compliance, transfer, or appeal-like cases |
| references/qa-checklist.md | Before finalizing an output or auditing a draft response |
Use sources in this order:
If a policy detail may have changed, verify the current journal page before giving final submission advice.
2f7766f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.