hermes

Write a results section

Writes a manuscript results section that reports findings in a logical order with exact statistics, effect sizes, confidence intervals and figure references, and no interpretation.

context

A results section reports what was found, in the order the questions were asked, so a reader can check every claim against the numbers. Editors and statistical reviewers look for: participant flow and sample characteristics first; the primary outcome before secondary and exploratory ones; for each estimate, the effect size with its confidence interval, the test statistic, degrees of freedom and exact p value (p < .001 below that); the same precision throughout; non-significant results reported as fully as significant ones; and pre-specified and post hoc analyses clearly separated. Interpretation, comparison with other studies and speculation belong in the discussion.

task

Write the results section from this outputOnly if [REPORTING_GUIDELINE] is given: , following .

results data

  1. Before writing, check the numbers for internal consistency: sample sizes that add up across groups and flow stages, percentages that match counts, p values consistent with the test statistic and degrees of freedom, confidence intervals that contain the point estimate, and means within the possible range of the scale. List every inconsistency instead of silently fixing it.
  2. Order the section: sample and participant flow, baseline characteristics (refer to the table), primary outcome, secondary outcomes, then sensitivity and exploratory analyses, each labelled as pre-specified or post hoc.
  3. For each result, write one or two sentences giving the direction and size of the effect in the outcome's units, the confidence interval, and the test details in the style required. Report non-significant results the same way, with their estimates and intervals.
  4. Refer to tables and figures by number, using placeholders like (Table 2) and (Figure 1), and keep numbers that are in a table out of the text unless they are the key result.
  5. Use subheadings that mirror the methods or hypotheses.
constraints
  • No interpretation: no "this suggests", "importantly", "interestingly", "as expected", no comparisons with other studies, no explanations of why.
  • Never describe a non-significant result as a "trend", "marginally significant" or "approaching significance". Report the estimate and interval and let the discussion handle it.
  • Do not use "significant" except in the statistical sense.
  • Do not round, recompute or change any number except to apply consistent decimal places, and say if you did. Do not invent any statistic that is not in the input; mark gaps as [MISSING: ...].
  • Use the past tense for findings.
  • If the primary outcome is not identified, ask for it, and order results by the hypotheses as given in the meantime.
  • If the results are qualitative (themes or categories), report each theme with its definition, how widely it occurred in the terms the author used, and supporting quotes taken word for word from the input, labelled with the participant codes given; replace the statistical consistency checks with a check that every quote and code appears in the input.
output format

Results

The section with subheadings and figure and table references.

Tables and figures referenced

List of each reference and what it must contain.

Consistency checks

Each check and its outcome; inconsistencies first.

Missing information

Each [MISSING] item and what is needed.

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
Intermediate
made for
Researcher / scientist, Student
risk
read-only
version
v1.1.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 write-results-section --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-results-section -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.

PromptScientific writing

Write a replicable methods section

Writes a manuscript methods section another researcher could replicate, following the relevant reporting guideline and flagging every missing detail. For authors drafting a paper or thesis.

write-methods-section
PromptScientific writing

Write a discussion section

Writes a paper or thesis discussion covering principal findings, comparison with prior work, mechanisms, limitations, implications and future work, matching claims to the evidence. For authors.

write-discussion-section
PromptScientific writing

Plan the figures for a paper

Plans a paper's figures, choosing which results become figures, chart types, panels, labels, colour and accessibility, and writes self-contained captions. For authors preparing a manuscript.

design-scientific-figures
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
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
RuleScientific writing

Academic 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-rules