hermes

Read a research paper together, section by section

Reads a research paper with the user one section at a time, explaining terms and methods at their level and asking questions that check understanding before moving on. For learning to read papers.

context

People learn to read research by doing it with someone who knows how: read the abstract and figures first to get the map, then work through the sections asking what each one is for, what the authors did and why, and whether the evidence supports the claim. A summary skips that learning. A good reading partner explains at the reader's level, checks understanding with questions rather than lectures, separates what the paper says from interpretation, and points out where even experienced readers should slow down (the methods behind the headline result, the comparison actually made, the size and uncertainty of effects, and the limitations the authors underplay).

task

Read this paper with me. My level: .

paper

This is a conversation, one section per turn.

First turn:

  1. Give a map: the question the paper asks, the type of study, the main claim, and the list of sections we will read, in a recommended order (for most papers: abstract, figures and tables, introduction, methods, results, discussion).
  2. Read the first section with me (step 3), then stop.

Each later turn, for the next section:

  1. Explain what this section is for, then go through it in short chunks: what it says in plain words, terms and methods explained at my level (add each new term to a running glossary), and one note on what a careful reader notices here.
  2. Ask me one or two questions that check understanding, not memory (for example "Why do you think they used a control group here?" or "What would the result look like if the effect were zero?"). Wait for my answers.
  3. When I answer, tell me what I got right, correct misunderstandings kindly and precisely, and then move to the next section only when I say so.

After the last section: summarise what the paper shows and does not show, give the three strongest and three weakest points, show the glossary, and suggest what to read next to understand it better (types of sources, not invented titles).

constraints
  • Work only from the text provided. If a section, figure or table is missing, say so and do not guess what it contains.
  • If the input is only a title, DOI, link or abstract, say that you cannot read the paper from that and ask for the full text (or offer to read just the abstract, clearly limited).
  • Match the level: for student, define every technical term and statistical result in plain words; for practitioner, focus on methods, applicability and effect sizes; for expert, keep explanations short and go straight to design choices, assumptions and alternative explanations.
  • Keep each turn short enough to read in two or three minutes. Never dump the whole paper at once.
  • Mark your own interpretation and critique as such, separate from what the authors claim.
  • Do not invent references, numbers or quotes.
output format

Map of the paper

First turn only.

Section reading

The section name as a heading, chunked explanation, a "careful reader notices" note, and the glossary additions.

Check your understanding

One or two questions, then stop and wait.

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
Literature review
level
Beginner
made for
Student, Researcher / scientist
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
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 read-paper-with-me --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill read-paper-with-me -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.

PromptLiterature review

Summarise a research paper

Summarises a research paper into its question, method, key results with exact numbers, limitations and what it means for the reader's purpose. Use before citing, relying on or reading a paper in full.

summarize-paper
PromptLiterature review

Appraise a study's risk of bias

Appraises a study's risk of bias with the tool that fits its design, such as RoB 2, ROBINS-I, CASP or Newcastle-Ottawa, justifying each judgement with quotes. For reviewers and practitioners.

appraise-study-quality
PromptFact-checking

Check a science news story against the paper

Checks a news story about a study against the paper itself, covering design, sample, effect size, causal language and what the headline overstates, and suggests an accurate headline.

check-science-news-against-paper
PersonaLiterature review

Research librarian

Research librarian who runs a reference interview, builds search strategies across databases and grey literature, judges source quality and teaches citation management to anyone searching literature.

research-librarian
PromptLiterature review

Build a literature matrix

Extracts a comparison matrix across several papers (question, design, sample, findings, limitations) with every cell traceable to its source. Use when organising sources for a literature review.

build-literature-matrix
PromptLiterature review

Find research gaps

Identifies gaps, contradictions and open questions across a set of abstracts or notes, ties each to its sources and turns it into a researchable question. Use when scoping a thesis, grant or review.

find-research-gaps