mcpField
D
data-storytelling

data-storytelling

github.com/wshobsonData & databases41.9k17.1k installsUpdated 2w ago
Repository

About data-storytelling

A reference skill for turning data into narratives that support decisions and motivate action. It combines story structure, audience-aware communication, and guidance on using data and visuals to present insights and recommendations.

Key features

  1. 01Story structure and narrative arc
  2. 02Data, narrative, and visuals framework
  3. 03Audience-focused communication
  4. 04Insight-led reporting guidance
  5. 05Recommendations and next steps

Use cases

  1. 01Presenting analytics to executives
  2. 02Preparing quarterly business reviews
  3. 03Creating investor presentations
  4. 04Writing data-driven reports

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wshobson/agents --skill data-storytelling

After installing, type/data-storytellingin Claude Code to confirm it loaded.

Bundled filesreferences/details.md

Details

From the project README

Data Storytelling

Transform raw data into compelling narratives that drive decisions and inspire action.

When to Use This Skill

  • Presenting analytics to executives
  • Creating quarterly business reviews
  • Building investor presentations
  • Writing data-driven reports
  • Communicating insights to non-technical audiences
  • Making recommendations based on data

Core Concepts

1. Story Structure
Setup → Conflict → Resolution

Setup: Context and baseline
Conflict: The problem or opportunity
Resolution: Insights and recommendations
2. Narrative Arc
1. Hook: Grab attention with surprising insight
2. Context: Establish the baseline
3. Rising Action: Build through data points
4. Climax: The key insight
5. Resolution: Recommendations
6. Call to Action: Next steps
3. Three Pillars
PillarPurposeComponents
DataEvidenceNumbers, trends, comparisons
NarrativeMeaningContext, causation, implications
VisualsClarityCharts, diagrams, highlights

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

Do's
  • Start with the "so what" - Lead with insight
  • Use the rule of three - Three points, three comparisons
  • Show, don't tell - Let data speak
  • Make it personal - Connect to audience goals
  • End with action - Clear next steps
Don'ts
  • Don't data dump - Curate ruthlessly
  • Don't bury the insight - Front-load key findings
  • Don't use jargon - Match audience vocabulary
  • Don't show methodology first - Context, then method
  • Don't forget the narrative - Numbers need meaning

Comments

Markdown supported