Extract effect-size data for a meta-analysis
Builds a data-extraction form and extracts effect-size inputs from study reports with their locations, logging every conversion and flagging missing statistics. For meta-analysis teams.
Extraction errors are common in meta-analyses and often go unnoticed: a standard error copied as a standard deviation, a change score mixed with a final value, the wrong time point, a per-protocol number used where intention-to-treat was planned, or a cluster trial treated as individually randomised. Good practice is a piloted form, duplicate extraction, a recorded source location for every number, and an explicit log of every derived value and the formula used, so a second extractor and the reader can check it. Missing statistics are requested from authors or handled by a pre-specified method, never filled in by guesswork.
Extract data for the outcome "" from these studies.
- Build the extraction form for this outcome: study identifiers, design and unit of randomisation, population, arms and their definitions, time point, analysis population (ITT or per protocol), measure and direction (whether higher is better), and the statistics needed for the outcome type (continuous: n, mean, SD per arm or a between-group difference with its CI or SE; binary: events and n per arm; time-to-event: HR with CI), plus adjusted or unadjusted, and notes.
- Extract every field for each study, quoting the location (section, table or figure) for each number. Use "not reported" when absent. When several candidates exist (time points, scales, analysis sets), list them and say which matches the outcome definition and why.
- Where the needed statistic is not reported directly but can be derived, derive it and log it: SD from SE (SD = SE × √n), SD from a 95% CI of a mean (for large samples, SD = √n × (upper − lower) / 3.92, using the t distribution for small samples), SE of a difference from its CI or from an exact p value and test statistic, and standardised mean differences from t or F for two groups. For medians with IQR or range, flag skew, name the estimation method if one is used, and recommend a sensitivity analysis excluding the estimated values.
- Flag unit-of-analysis issues: cluster designs (needs the ICC or a design effect), crossover trials, multi-arm trials sharing a control group, and multiple outcomes from the same participants.
- Where inputs are complete, compute the effect size the user's outcome implies (for example Hedges' g with its variance, mean difference, log odds ratio or log risk ratio) and show the inputs. Mark these as needing verification in statistical software.
- Never estimate, impute or "approximately read" a number that the text does not give or that cannot be derived exactly from given numbers. Graph-only data are marked "figure only; digitise with a plot-digitising tool and record it".
- A p value reported as "p < 0.05" cannot be used to derive a statistic; say so.
- Keep the direction of effect consistent across studies and record when a scale had to be reversed.
- Show every calculation with its inputs so a second extractor can check it.
- If a study's text is too partial to extract from, say what is missing rather than extracting from the abstract alone without saying so.
Extraction form
A table: field | definition | allowed values.
Extracted data
One table per outcome: study | design | arm | n | statistic(s) | time point | analysis set | location.
Conversions log
Numbered: study | derived value | formula | inputs | result.
Missing or unclear
Per study: what is missing, whether to contact authors, and the exact request to send.
Effect sizes
A table of computed effects with variance or CI, or "not computable" with the reason.
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Research and science
- category
- Literature review
- level
- Expert
- made for
- Researcher / scientist, Student, Data 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
use in
npx @hermes-hq/hodios install extract-data-for-meta-analysis --target claude-codenpx skills add hermes-hq/hodios-dist --skill extract-data-for-meta-analysis -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 Literature reviewPlan and interpret a meta-analysis
Plans and interprets a meta-analysis, deciding whether to pool, the effect measure and model, heterogeneity, subgroup and sensitivity analyses, publication-bias checks and certainty. For review teams.
plan-meta-analysisAppraise 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-qualityBuild 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-matrixWrite a systematic review protocol
Writes a PROSPERO-style systematic review protocol with the question, eligibility criteria, search, screening, extraction, risk of bias and synthesis plan, following PRISMA-P. For review teams.
write-systematic-review-protocolConsulting 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.
statisticianFind 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