More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Data Stories Executives Actually Understand

    1

    Turn quarterly numbers into a readout that ends in a decision: a setup-tension-resolution shape, a five-move arc, one message per chart, and honesty rules that keep the story true.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Data Stories Executives Actually Understand

    Data Stories Executives Actually Understand

    Example session with this skill installed

    I run a fictional regional bakery chain called Ember Crumb with 14 shops. Quarterly numbers show total revenue flat, but something feels off. Build me the story for the quarterly review — hook, context, build, climax, and the ask. Invent plausible numbers.

    • Read your context and instructions
    • Compiled the data stories executives

    STORY BRIEF — Ember Crumb quarterly review, invented numbers for this demo only. Audience: the chain's owners. Decision needed: approve a Saturday staffing pilot.

    HOOK: "We lose an estimated $96,000 a year to Saturday mornings — and the fix is people, not marketing."

    CONTEXT: Total revenue is flat at $3.1M for the quarter, which looks unremarkable. A bar chart shows Ember Crumb against two fictional peer chains, all flat. The flat headline hides the problem, which is why the hook comes first.

    BUILD — three charts, one message each. A line chart shows revenue by day of week: Saturday down 18% against last year, every other day within 3% of flat. A bar chart shows Saturday revenue by hour: 7–10 a.m. down 31%, the rest of Saturday down only 4%. A stacked bar shows Saturday morning sales by product: pastries down 34%, bread flat — the ovens run, but the pastry case empties before 9 a.m. and is not refilled until noon.

    CLIMAX: "This is not a demand problem. It is a Saturday-morning staffing problem — the case empties before the morning crowd arrives, and nobody is there to refill it."

    RESOLUTION AND ASK: "Fund two extra Saturday morning staff at the six busiest shops. Cost: an estimated $74,000 a year. If it recovers a third of the lost Saturday morning sales, it pays for itself in under a year. Decision needed: approve the pilot at three shops this quarter."

    COUNTER-EVIDENCE SHOWN: Sunday revenue rose 8%, which rules out a weekend-wide decline and sharpens the Saturday story. NOT CLAIMED: the deck does not claim the staffing will recover the sales — it claims the pilot will test whether it does, measured against matched control shops.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Data does not persuade; stories about data do. This skill builds the story honestly, with the narrative serving the data and never the reverse. Every story runs three beats: setup gives the baseline, tension names the gap between expected and actual, and resolution ends in a recommendation with a concrete next step. Longer readouts expand into five moves — hook, context, build, climax, and resolution with an ask — and the climax is a single quotable sentence written before the presentation, not discovered during it. Chart discipline keeps each chart to one message: the chart form follows the message, titles state conclusions instead of describing charts, key numbers are labeled directly, and counter-evidence is shown rather than hidden. A story brief template locks in the audience, the decision needed, the hook, the climax, the ask, and what is deliberately not claimed. The honesty rules are blunt: never cherry-pick a timeframe, distinguish suggests from proves, say so when the data supports no recommendation, and run one story per presentation.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Writing & Content.

    • It cannot create a story from numbers you do not supply, and it never invents or smooths data to fill a gap.
    • If no real tension exists in the data, the honest output is a status update, not a forced story arc.
    • It produces the story brief and chart plan, not finished slides or rendered charts.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Then the honest output is a status update with the numbers and no forced arc. A forced arc on flat data teaches the audience to distrust the next real story.

    No. Show it. A story that hides inconvenient data collapses in questions, and the collapse costs more credibility than the inconvenient segment ever would.

    It produces the story brief, the chart set with one message per chart, the climax sentence, and the recommendation with its ask. Turning that into finished slides is your step, using the brief as the spec.

    New in Writing & Content