hermes

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

context

Editors value reviews that show the reviewer understood the paper, separate fatal problems from fixable ones, explain why each issue matters, and say what would resolve it. Authors value reviews that are specific and respectful. Weak reviews are vague ("the methods are unclear"), demand a different study, insist on citing the reviewer's own work, or nitpick style while missing a design flaw. Peer-review manuscripts are confidential, and many publishers restrict uploading them to AI tools, so the reviewer remains responsible for following the venue's policy and for every judgement in the report.

task

Review this manuscriptOnly if [VENUE] is given: submitted to :

manuscript

Only if [FOCUS] is given: Give extra attention to:

  1. Before judging, summarise the paper's question, design, main findings and claimed contribution in your own words.
  2. Assess whether the question matters and whether the contribution is new, judging only from what the manuscript itself shows and cites.
  3. Check the methods against the question: design, sample and power, measures, controls, analysis choices, handling of missing data and multiple comparisons, and whether the conclusions follow from the results. Name the reporting guideline that applies (for example CONSORT, STROBE, PRISMA, ARRIVE, COREQ, TRIPOD) and note the important items missing.
  4. Check reproducibility: availability of data, code and materials, and whether the methods are described well enough to repeat.
  5. Sort issues into major (could change the conclusions or the decision) and minor (clarity, presentation, small analyses). For each major issue give the location, the problem, why it matters and what would resolve it.
  6. Make a recommendation (accept, minor revision, major revision or reject) that follows from the major issues.
constraints
  • Every issue points to a specific section, table, figure or line and proposes a resolution. No vague criticism.
  • Stay within the paper's aims: do not ask for a different study, and request new experiments or data only when the conclusions cannot stand without them.
  • Do not ask the authors to cite particular papers unless a missing citation is needed for a specific claim, and never suggest references you cannot verify.
  • Be respectful and impersonal: critique the work, never the authors. Acknowledge real strengths.
  • Do not speculate about the authors' identity or intentions. Raise suspected misconduct (duplicated images, impossible numbers, plagiarism) only in the confidential comments, with the evidence.
  • If the text provided is only part of the manuscript, say so and limit the review to what you can see.
  • Start the report with one line reminding the reviewer to check that the venue permits AI assistance and to keep the manuscript confidential.
output format

One reminder line, then:

Summary

One paragraph.

Overall assessment

Strengths and the main concerns in three to five sentences.

Major issues

Numbered: location — problem — why it matters — what would resolve it.

Minor issues

Numbered, one or two lines each.

Reporting and reproducibility

The guideline that applies, missing items, and data and code availability.

Recommendation

The recommendation and the two or three reasons that decide it.

Confidential comments to the editor

Anything not for the authors, or "None".

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
Peer review
level
Expert
made for
Researcher / scientist
risk
read-only
version
v1.0.0 · 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

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install write-peer-review --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-peer-review -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the research-science plugin
claude plugin install hodios-research-science@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Peer review
PromptScientific writing

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.

respond-to-reviewers
PersonaResearch methods

Research methodologist

Research methodologist who probes study designs for validity threats, matches methods to questions and asks what evidence would change the conclusion. Use as a sparring partner for any study.

research-methodologist
PersonaStatistics

Consulting statistician

Consulting statistician who asks how the data were produced before analysing them, chooses methods that fit the question, checks assumptions and refuses to over-claim. Use for any data analysis.

statistician
PromptPeer review

Assess a paper's reproducibility

Assesses a paper's reproducibility, covering data and code availability, methods detail, materials, preregistration and computational environment, and lists what a replicator would be missing.

assess-reproducibility
PromptPeer review

Check a manuscript against its reporting guideline

Checks a manuscript against its reporting guideline, such as CONSORT, PRISMA, STROBE, ARRIVE or COREQ, item by item, and lists what is missing and where to add it. For authors and reviewers.

check-manuscript-reporting
PersonaPeer review

Peer reviewer

Fair, rigorous peer reviewer who separates fatal flaws from fixable issues, checks every claim against its evidence and writes respectful, actionable reviews. For refereeing and pre-submission reads.

peer-reviewer