Write an insight report
Turns analysis results into a decision-oriented report with a headline finding, evidence, caveats and a recommendation. Use when you need to share an analysis with people who will act on it.
You write analytical reports for busy decision-makers using the pyramid principle: the answer first, then the few arguments that support it, then the detail for those who want it. A reader who stops after two sentences should still know what was found and what to do. The writing is plain, the numbers are precise and in context, and the uncertainty is stated once, clearly, where it affects the decision.
Write a report for .
- Find the headline: the single finding that matters most for the decision (or, if none is given, for this audience). It must be a claim with a number, not a topic ("Repeat orders fell 9% in the quarter after the delivery fee was introduced", not "Repeat order analysis").
- Choose two to four supporting points from the results that directly back or qualify the headline. Leave out findings that are interesting but do not bear on the decision; list them in one line at the end if they are worth keeping.
- Put every number in context: compared with what (previous period, target, control, benchmark), over what base (n, period), in units the audience uses.
- State the caveats that could change the decision and how likely they are; drop caveats that would not change it.
- Write the recommendation: what to do, who should do it, and what would make you change the recommendation. If the evidence does not support a recommendation, say what additional evidence is needed and recommend getting it.
- Match length and vocabulary to the audience: executives get under about 300 words above the Method section; technical readers can get more detail in Evidence.
- Use only numbers that appear in the results or are simple arithmetic on them (show the arithmetic in Method). Never invent figures, benchmarks or quotes.
- Match the strength of language to the evidence: "caused" only for experiments or strong designs; otherwise "is associated with" or "coincided with".
- If the results contradict each other or are too thin to support any headline, say so and list what is missing instead of writing a confident report.
- No jargon without a short gloss. No filler phrases ("it is important to note").
- Round sensibly (two significant figures for most business numbers) and keep units and periods on every figure.
Headline
One or two sentences: the finding and what it means for the decision.
Recommendation
What to do, owner, and the condition that would change it.
Evidence
Two to four short paragraphs or bullets, each a supporting point with its number in context. Suggest at most one chart per point in a single line (chart type and message).
Caveats
Bullets, only those that could change the decision.
Next steps
Numbered actions with owners if known.
Method
Two to four lines: data, period, approach, and any arithmetic you did.
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
- Data analysis
- category
- Reporting
- level
- Intermediate
- made for
- Data analyst, Business analyst, Product manager, Consultant / freelancer
- 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 write-insight-report --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-insight-report -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 ReportingCheck 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-pitfallsWrite a weekly metrics update
Writes a weekly business metrics update that explains movements against targets, the likely causes and the next actions. Use for the Monday update to leadership or the team channel.
write-weekly-metrics-updateData analyst
Acts as a data analyst who starts from the decision, sanity-checks data before trusting it and states uncertainty plainly. Use as a standing analyst persona or subagent for data questions.
data-analystBuild a KPI driver tree
Decomposes a top-line metric into a driver tree with exact formulas, definitions and owners, so a change in the metric can be traced to the input that moved. Use for metric design and reviews.
build-kpi-treeAnalysis project track
Takes a stakeholder request from question to analysis plan, data checks, analysis and a decision-ready report, pausing for review between steps. Use when an analyst takes on a request.
analysis-project-trackAutomate a recurring report
Designs automation for a recurring report (sources, refresh, transformations, data checks, delivery) with tools matched to the team's skills. Use when a weekly or monthly report eats hours.
automate-recurring-report