hermes

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.

context

A useful paper summary lets the reader decide whether to rely on, cite or read the paper without misrepresenting it. Plain summaries tend to echo the abstract's framing, drop the numbers, blur what was shown with what the authors speculate, and skip the limitations. This summary works from the text provided, keeps every number traceable to the paper, and ends with what the paper means for the reader's own purpose.

task

Summarise this paper at depth "":

paper

Only if [PURPOSE] is given: The reader's purpose:

  1. Name the paper type (randomised trial, observational study, lab experiment, simulation, qualitative study, systematic review, theory, methods paper…), because it decides which limitations matter.
  2. Extract the research question or hypothesis, the design, the sample or data (size, population, setting, period) and the main analysis.
  3. Extract the key results with their numbers exactly as reported: effect sizes, confidence intervals, p-values, accuracy, n. Say which outcomes were primary and which secondary or exploratory.
  4. Separate what the results show from what the authors infer or speculate in the discussion.
  5. List limitations: those the authors state and those you can see (design, sample, measurement, confounding, multiple comparisons, generalisability, funding or conflicts of interest). Label which is which.
  6. Relate the paper to the reader's purpose: what it supports, what it does not, and what to check next. Without a purpose, say who would find it most useful.

Depth: "abstract" is about 150 words in one paragraph; "standard" about 400 words; "deep" up to 1,000 words and adds methods detail (measures, controls, statistical model), whether the conclusions follow from the results, and three questions you would ask the authors.

constraints
  • Use only the text provided. If it is only an abstract or an excerpt, say so in the first line and write "not in the text provided" wherever the full paper would be needed.
  • Copy every number from the paper. Never round, recompute or infer one. If a result is reported without a number, describe it in words and say the number is not given.
  • Never strengthen a claim: "associated with" stays associated, a pilot stays a pilot, a mouse study stays a mouse study.
  • If you receive only a title, citation, DOI or link and cannot read the text, ask for the full text or abstract and stop. Do not summarise from memory.
  • Keep the authors' terms for key constructs and define jargon in a few words on first use.
output format

Citation: authors, year, title and venue as given (omit what is missing). Paper type: one phrase.

Question

One or two sentences.

Method

Bullets: design, sample, data, analysis.

Key results

Bullets, each with its number(s) and "(primary)" or "(secondary)".

Limitations

Bullets, each tagged "(authors)" or "(reviewer)".

What it means for you

Two to four sentences tied to the purpose.

For depth "abstract", keep the citation line and write the five parts as one paragraph with bold inline labels instead of headings.

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
Intermediate
made for
Researcher / scientist, Student
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 summarize-paper --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill summarize-paper -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

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
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
PromptLiterature review

Write a literature review section

Synthesises sources into a thematic literature review section with in-text citations and a reference list, organised by idea rather than paper by paper. Use for theses, articles and proposals.

write-literature-review-section
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
PromptLiterature review

Build a database search strategy

Builds a Boolean search strategy for PubMed, Scopus, Web of Science or Google Scholar with concepts, synonyms, controlled vocabulary, filters and a search log. For systematic and narrative reviews.

build-search-string