skills / data

data-storytelling

what it does

Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Turn this into a short update for our CEO.”

Source material given with the request

Quarterly numbers, Q2 2026 -> Q3 2026 (Holloway, B2B scheduling software) Total revenue: $4.10M -> $4.35M Enterprise revenue: $2.60M -> $2.95M SMB revenue: $1.50M -> $1.40M Enterprise monthly logo churn: 0.8% -> 0.7% SMB monthly logo churn: 3.1% -> 5.4% New SMB signups per month: 410 -> 405 SMB median first support response: 4 h -> 19 h (support moved to an enterprise-first queue in July) Data source: billing warehouse, finance-reconciled. Churn = accounts cancelled / accounts at start of month.
with the skill
# Q3 update: Enterprise is carrying growth while SMB retention is breaking **Headline:** Revenue grew 6% to $4.35M, but SMB monthly churn jumped from 3.1% to 5.4% after our July support change. If it persists, it will erode the SMB base. | | Q2 | Q3 | Change | |---|---|---|---| | Total revenue | $4.10M | $4.35M | +6.1% | | Enterprise revenue | $2.60M | $2.95M | +13.5% | | SMB revenue | $1.50M | $1.40M | -6.7% | | Enterprise monthly churn | 0.8% | 0.7% | -0.1 pt | | SMB monthly churn | 3.1% | 5.4% | +2.3 pts | | SMB median first support response | 4 h | 19 h | ~4.8x slower | | New SMB signups / month | 410 | 405 | roughly flat | **What the data shows** - **Enterprise is healthy.** Revenue is up $350K and churn improved slightly, so the enterprise-first support queue hasn't hurt that segment. - **SMB is losing customers, not failing to attract them.** Signups are flat (410 → 405 per month), so the $100K revenue drop comes from retention. - **The timing lines up with the support change.** Support moved to an enterprise-first queue in July, and SMB first response went from 4 h to 19 h. At 5.4% monthly churn, SMB would lose roughly half its accounts over a year, versus about a third at 3.1%. **Caveat:** This is a strong timing correlation, not proven causation. We haven't yet checked whether the churned SMB accounts were the ones who waited longest for support.
Show the rest (7 more lines)
**Recommendation** 1. **This week:** Pull the Q3 SMB cancellations and compare churn for accounts that filed tickets (and how long they waited) against those that didn't. That tells us whether support is the cause. 2. **In parallel:** Set an SMB response-time target, such as a dedicated or reserved SMB queue, rather than waiting for the analysis to finish. The cost of waiting is another quarter at elevated churn. **Decision needed:** Approve a support routing or staffing change for SMB, with the cohort analysis reported back in two weeks. *Source: billing warehouse, finance-reconciled. Churn = accounts cancelled ÷ accounts at start of month.*
without
**Subject: Q3 update: growth is enterprise-led, SMB retention is deteriorating** **Headline:** Revenue grew to $4.35M in Q3, up 6.1% from $4.10M in Q2. Enterprise growth is masking a sharp SMB decline. **Numbers** - **Enterprise:** $2.95M, up 13.5% from $2.60M. Monthly logo churn improved slightly, from 0.8% to 0.7%. - **SMB:** $1.40M, down 6.7% from $1.50M. Monthly logo churn jumped from 3.1% to 5.4%. - **SMB acquisition is steady:** 405 new signups per month, versus 410 in Q2. The SMB decline is a retention problem, not a demand problem. **Likely cause:** SMB median first support response time rose from 4 hours to 19 hours after support moved to an enterprise-first queue in July. The timing lines up with the churn spike, but we haven't yet confirmed that it's the driver. **Recommendation:** Treat SMB churn as the priority issue. Next steps: 1. Check whether churned SMB accounts were disproportionately ones that had waited on support. 2. Consider adjusting the queue, for example with an SMB response-time target or dedicated capacity, while we confirm. *Source: billing warehouse, finance-reconciled. Churn = accounts cancelled ÷ accounts at start of month.*

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
allhands-nps-not-comparable

“Draft the three slides for Friday's all-hands about our jump in customer satisfaction.”

board-story-opt-in-feature

“I'm presenting this to the board on Thursday. Can you make the story more compelling?”

ceo-update-segment-split

“Turn this into a short update for our CEO.”

chart-for-channel-mix

“I need one chart for the board deck showing how our signup mix shifted this year. What chart should I make and how should I set it up?”

slide-titles-takeaways

“My slide titles are boring. Can you rewrite them so each one says what the slide shows?”

Install

Download the .zip and unzip it. Put its files, in a folder named data-storytelling, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.