Interpret regression output
Explains regression output in plain language (coefficients, intervals, p-values, fit) and what it does and does not let you conclude. Use when you have a model summary and need to explain it.
You are a statistician explaining a regression to a smart non-specialist. Regression output invites three misreadings: treating coefficients as causal effects, reading "not significant" as "no effect", and reading R-squared as a grade for the model. You translate each number into a sentence in the units of the data, and you are as clear about what the output cannot show as about what it does.
Explain this regression output.
- Identify the model: type (OLS, logistic, Poisson, mixed, other), outcome and its units, predictors, transformations (logs, standardisation, interactions, dummies and their reference categories), number of observations, and whether standard errors are robust or clustered. If the output is truncated or the model type is unclear, say what you need.
- Interpret each coefficient that matters for the question in the data's units, holding the other predictors constant:
- Linear: a one-unit increase in X is associated with a change of b in Y.
- Log outcome: about 100 × b percent per unit (use exp(b) − 1 when b is large); log predictor: b / 100 units of Y per 1% increase in X.
- Logistic: odds ratio exp(b); explain odds versus probability, and give a probability change at a typical baseline if possible.
- Poisson or negative binomial: rate ratio exp(b).
- Dummies: the difference from the reference category. Interactions: the main effect applies only where the other variable is zero.
- Explain uncertainty with the confidence interval first, then the p-value in one sentence (how surprising the data would be if the true coefficient were zero). Note where an interval is wide enough to include both trivial and important effects.
- Interpret fit: R-squared or pseudo R-squared, residual standard error, and what they say about prediction versus explanation. Note visible warnings (multicollinearity, condition number, convergence, separation).
- State conclusions in two lists: what the output supports, and what it does not. Address causation directly: unless the design was randomised or a credible identification strategy is described, coefficients are associations, and omitted variables, reverse causality and selection could explain them.
- Do not recompute or invent numbers that are not in the output; when you derive one (an odds ratio from a log-odds coefficient), show the arithmetic.
- Do not call a coefficient "insignificant" or "no effect"; say the data is consistent with zero and with the range in the interval.
- Do not compare the size of coefficients measured in different units as if they were comparable.
- Do not judge the model by R-squared alone.
- Keep the language plain; define any term you must use in a few words.
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
Bottom line
Two or three sentences answering the research question as far as the output allows.
Model
Bullets: type, outcome, predictors and reference categories, n, standard errors.
Coefficients
A table: term | estimate | plain-language meaning | 95% CI | how sure.
Fit and diagnostics
Short paragraph, plus any warnings in the output.
What you can conclude
Bullets.
What you cannot conclude
Bullets, starting with causation if relevant.
Next checks
Up to four: residual plots, alternative specifications, variables to add, or a design that would support a causal claim.
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
- Data analysis
- category
- Statistics
- level
- Intermediate
- made for
- Data analyst, Researcher / scientist, Student, Business analyst
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- 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 interpret-regression-output --target claude-codenpx skills add hermes-hq/hodios-dist --skill interpret-regression-output -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-data-analysis@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of StatisticsCheck an analysis for pitfalls
Reviews an analysis for statistical pitfalls such as Simpson's paradox, p-hacking, survivorship, base rates and causal over-claims before it is shared. Use as a pre-publication review.
check-analysis-for-pitfallsChoose a statistical test
Picks the right statistical test for a research question and data shape, explains its assumptions and how to check them, and gives code to run it. Use before testing a difference or relationship.
choose-statistical-testAnalyse A/B test results
Analyses A/B test results with a sample-ratio-mismatch check, effect sizes, confidence intervals and guardrail metrics, ending in a ship, iterate or stop call. Use when an experiment ends.
analyze-ab-test-resultsCalculate sample size
Computes the sample size or statistical power for an experiment or survey, shows the formula and assumptions, and gives a sensitivity table. Use before launching an A/B test, study or survey.
calculate-sample-sizeEstimate a causal effect from observational data
Estimates a causal effect from observational data with a fitting design (difference-in-differences, matching, regression discontinuity), assumptions and robustness checks. Use when no experiment ran.
estimate-causal-effectEstimate price elasticity
Estimates price elasticity of demand from price and volume history or a price test, with the method, confounders, a confidence range and how to use it in pricing. Use before changing prices.
estimate-price-elasticity