Respond to peer reviewers
Drafts a point-by-point response to peer-review comments, giving the change made or a polite, evidenced rebuttal for each, never claiming unmade changes. Use for revise-and-resubmit.
Editors read the response letter to decide whether the authors took the reviews seriously, and reviewers check that every point was answered and that each answer matches the revised manuscript. Good responses quote each comment, answer it directly, say exactly what changed and where, and disagree only with evidence and courtesy. Letters fail when they skip or merge points, are defensive, thank the reviewer in every line, or claim changes that are not in the manuscript.
Draft a response to these reviews:
Only if [MANUSCRIPT_CHANGES] is given: Changes made or planned, and the authors' positions:
- Split the reviews into individual comments, numbered by reviewer (R1.1, R1.2, R2.1…), and split multi-part comments into separate points. Include the editor's own requests as E.1, E.2.
- Triage each comment: type (major, minor, clarification, typo), proposed action (accept, partially accept, rebut), and effort (low, medium, high).
- For each comment, write the response: a direct answer in the first sentence, then the change made with its location, or, for a rebuttal, the reason with evidence (data, analysis, citations from the authors' material), and any concession or compromise offered.
- Where reviewers conflict, say so to the editor and explain which way you went and why.
- Write a short opening paragraph to the editor summarising the main changes.
- Claim a change only if it appears in the authors' changes. Where you have no information, write a proposed response marked "[AUTHOR TO CONFIRM: proposed change …]" so nothing is promised by accident.
- Quote every reviewer comment verbatim; never paraphrase it in a way that changes its meaning, and never leave one out.
- Do not invent analyses, results, references or page numbers. Use "[page/line]" placeholders.
- Be courteous and specific. Thank the reviewers once in the opening, not in every response. Concede valid points plainly. Never be sarcastic, never question the reviewer's competence.
- A rebuttal needs a reason a reasonable reviewer could accept. If the only reason is effort, say so honestly and offer a limitation statement instead.
Triage
A table: ID | summary of the comment (under 12 words) | type | action | effort.
Response letter
The opening paragraph to the editor, then for each comment: R1.1 > The reviewer's comment, quoted verbatim.
Response: the answer. Change: what changed and where, or "No change" with the reason.
Open items
A checklist of every "[AUTHOR TO CONFIRM]" and placeholder, plus any comment that needs new analysis or data.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Research and science
- category
- Scientific writing
- level
- Expert
- made for
- Researcher / scientist, Student
- risk
- read-only
- version
- v1.0.1 · experimental
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install respond-to-reviewers --target claude-codenpx skills add hermes-hq/hodios-dist --skill respond-to-reviewers -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-research-science@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Scientific writingWrite a peer review
Writes a constructive manuscript review with a summary, major and minor issues, methodological and reporting concerns, and a reasoned recommendation. Use when refereeing a paper.
write-peer-reviewWrite a paper abstract
Writes a structured or unstructured abstract within a word limit from a manuscript, keeping every number faithful to the source and showing where each appears. Use before submission.
write-abstractExplain research to the public
Turns a research paper into an accurate plain-language summary, press release, blog post or social thread without hype, keeping caveats, study type and effect sizes. Use for science communication.
explain-research-to-publicWrite a research proposal
Writes a research or grant proposal section (aims, significance, approach, timeline) mapped to the funder's criteria, with placeholders instead of invented data. Use for grant or thesis proposals.
write-research-proposalAcademic writing rules
Standing rules for academic writing that hedge claims to the evidence, define terms, forbid invented citations, keep tense and terminology consistent, and report numbers precisely.
academic-writing-rulesShortlist target journals for a manuscript
Shortlists journals for a manuscript by scope, audience, article type, open-access costs and timelines, ranked in tiers, with facts to verify on each journal's site. For authors before submission.
choose-target-journal