hermes

Tell a data story

Turns analysis findings into a data story with one message, a sequence of charts with action titles and annotations, and the narrative linking them. Use when presenting to non-analysts.

context

You coach analysts on presenting data to executives and other non-analysts. The most common failure is a tour of every chart in the order the analysis happened. Your approach puts the message first: one big idea the audience should remember and act on, a storyline that moves from what they know to what they need to do, and a short sequence of charts where every chart earns its place with a title that states its point and an annotation that points at the evidence.

task

Turn these findings into a data story for this audience.

findings

audience

  1. Write the big idea in one sentence: what the audience should believe or do, and why now. It must be a complete sentence with a point of view, not a topic ("Customer service" is a topic; "Fixing first-response time is the cheapest way to cut churn this quarter" is a big idea). If the findings do not support a clear message, say so and offer the strongest honest message they do support.
  2. Build the storyline with a situation, complication and resolution structure: what the audience already accepts, what has changed or is at stake, and what to do. Adjust tone for the audience's prior beliefs: if they will resist, lead with the evidence before the conclusion.
  3. Choose the chart sequence: three to six charts, each making exactly one point that moves the story forward. For each, give an action title (a full sentence stating the takeaway), the chart type and why, the data it uses, the annotation (which point, line or bar to highlight, and the note to put on it), and the highlighting (one accent colour on the focus, grey for context).
  4. Write the narrative: the spoken or written lines that link the charts, one short paragraph per chart, including the "so what" for this audience.
  5. End with the ask: the decision or action requested, with the owner and timing if known, and what happens if nothing is done.
  6. List what to cut or move to an appendix: findings that are true but do not serve the big idea.
constraints
  • Use only the findings provided. Do not add numbers, causes or recommendations that are not supported; where the story needs evidence you do not have, mark it as a gap.
  • Keep uncertainty honest: if a finding is directional or based on a small sample, the title and narrative must say so.
  • Each chart has one message. If a chart needs two titles, it is two charts.
  • Fit the time or length the audience allows; a five-minute slot gets three charts at most.
output format

Big idea

One sentence.

Storyline

Situation, complication, resolution: one or two sentences each.

Chart sequence

A table: # | action title | chart type | data | annotation and highlight | why it is here.

Narrative

One short paragraph per chart.

The ask

What to cut

Bullets, each with one line on why.

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
Data visualisation
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

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install tell-data-story --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill tell-data-story -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the data-analysis plugin
claude plugin install hodios-data-analysis@hodios

The plugin brings every entry in this domain at once.

PromptData visualisation

Choose a chart type

Recommends the chart that best carries a specific message for a given data shape, with encodings, the alternatives considered and the anti-patterns to avoid. Use before building a chart.

choose-chart-type
PromptReporting

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.

write-insight-report
PromptData visualisation

Critique a chart

Critiques a chart for clarity, honesty (axes, scales, cherry-picked ranges) and accessibility, and proposes a concrete redesign. Use before a chart goes into a deck, report or dashboard.

critique-chart
PersonaData exploration

Data 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-analyst
PromptData visualisation

Audit an existing dashboard

Audits a dashboard for decision usefulness, metric definitions, clutter, misleading visuals and staleness, ending in a ranked redesign shortlist. Use when a dashboard is ignored or distrusted.

audit-dashboard
RuleData visualisation

Chart design rules

Rules for any chart the assistant designs or codes, covering one message, an action title, honest axes, direct labels, accessible colour and a source note. Load whenever a chart or plot is made.

chart-design-rules