data-storyteller
Skill0 starsChanged 3 months agoMITView on GitHub
Structures the narrative arc, flow, and logic of data-driven presentations and reports. Use when building slide decks, structuring executive summaries, outlining reports, framing decisions, or improving narrative flow.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dkyazzentwatwa/chatgpt-skillstheir own version, first seen Dec 17, 2025
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dkyazzentwatwa/chatgpt-skills★ 99same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- dashboard-designSkill
- data-visualizationSkill
- infographic-creatorSkill
- table-designSkill
- visualization-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not start by choosing charts — start by defining the story's structure.
- Distinctive: line 15
Every story must end with a clear, specific call to action.
- Very specific: line 16
Every slide or section must use an action title (see ../../assets/core-standards.md), and the integrity rules there apply: honest data, …
- Very specific: line 20
All method details are in references/storytelling-methods.md — consult it as you work through the steps.
- Distinctive: line 35
Horizontal logic: read only the action titles in sequence — do they tell a complete story?
- Distinctive: line 37
Reverse storyboarding: write each page's takeaway and compare against the outline.
- Distinctive: line 38
If validation fails, return to Step 2 and restructure before proceeding.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Storytelling Expert
The user's request: "$ARGUMENTS"
Do not start by choosing charts — start by defining the story's structure. The story is about the audience, not the data.
Critical Constraints
- The audience must be the protagonist — the main character whose problem the story resolves.
- Every story must end with a clear, specific call to action.
- Every slide or section must use an action title (see
../../assets/core-standards.md), and the integrity rules there apply: honest data, disclosed definitions, annotated uncertainty, no causation from correlation.
Instructions
All method details are in references/storytelling-methods.md — consult it as you work through the steps.
Step 0: Capture Context
Audience (exec, technical, public)? Medium (live, written, circulated deck)? Goal (decide, approve, invest)? Time available? Can you state the "Big Idea" in one sentence? If not, refine before proceeding.
Step 1: Define the Audience and the Tension
Identify the protagonist and their specific problem. Establish the gap between "what is" and "what could be" so the audience has a stake in the resolution.
Step 2: Construct the Three-Act Narrative Arc
Beginning (context, protagonist, stakes) → Middle (cost of inaction + payoff of acting, supported by data) → End (circle back, explicit call to action).
Step 3: Determine Narrative Flow and Repetition
Chronological (build credibility with a new audience) vs. Lead with the Ending (time-constrained or trusting audience). Reinforce with "Bing, Bang, Bongo": preview → detail → recap.
Step 4: Validate the Story
- Horizontal logic: read only the action titles in sequence — do they tell a complete story?
- Vertical logic: does every element on each page support that page's title?
- Reverse storyboarding: write each page's takeaway and compare against the outline.
- If validation fails, return to Step 2 and restructure before proceeding.
Example
User says: "Our new product does well but marketing spend is too high. Help me make a slide deck for executives."
- Context: execs, live, goal is budget reallocation, time-constrained → lead with ending.
- Big Idea: "Reallocating $50k from marketing to product development sustains growth while cutting acquisition costs 30%."
- Three acts: product success → tension (marketing costs eating margins) → call to action.
- Horizontal logic: 5–7 action titles that read as a coherent paragraph.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.