Skip to content
cccskills
FreePublished on GitHub

data-narrative-builder

Build compelling data-driven narratives. Use when presenting analysis results, creating stakeholder reports, or transforming a set of findings into a story that drives a specific decision or action.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md2.9 KB
  • assets/narrative_template.md1.9 KB
  • references/data_writing_guide.md2.9 KB
  • references/narrative_frameworks.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Data Narrative Builder

When to use

  • A presentation exists but feels like a data dump rather than a story
  • The analysis has a clear finding but the team doesn't know how to make it compelling
  • The audience is senior and will not read more than 5 slides
  • A decision needs to be made and the data needs to make a clear, emotion-aware argument
  • A recurring report needs to be restructured around a narrative rather than a metric list

Process

  1. Identify the central message — write the single most important thing the audience should know and do after seeing this. Everything else is supporting material. If there's more than one message, there are multiple presentations.
  2. Choose a narrative framework — select the structure that fits the context. Situation–Complication–Resolution works for most problem/solution stories. Before–After–Bridge is strong for demonstrating impact. See references/narrative_frameworks.md for all patterns with examples.
  3. Assign an emotional arc — map each section to an intended emotional state: establish comfort (Situation), introduce tension (Complication), offer confidence (Resolution). Tone and data emphasis should match the intended emotion at each stage.
  4. Draft each section with data woven in — apply the pyramid principle: lead with the conclusion, then support it with evidence. Numbers must serve the narrative, not interrupt it. Round large numbers for recall; humanise by expressing impact in terms the audience cares about.
  5. Plan the visual sequence — assign one key chart or visual to each narrative beat. The visual should reinforce the spoken or written message, not repeat it. See references/data_writing_guide.md for annotation and emphasis techniques.
  6. Write the opening hook and closing call to action — the hook must earn attention in under 10 seconds (a surprising stat, a question, or a contrast). The CTA must name a specific decision, person, and deadline. Complete assets/narrative_template.md.

Inputs the skill needs

  • The central finding or insight to be communicated
  • The audience (role, knowledge level, what they care about most)
  • The desired action or decision at the end of the presentation
  • All supporting data and charts already prepared
  • Format and time constraints (slides, report, 5-minute presentation, 30-page doc)

Output

  • references/narrative_frameworks.md — SCR, BAB, hero journey, and sparklines patterns with data storytelling examples
  • references/data_writing_guide.md — pyramid principle, number formatting, annotation, plain-language techniques
  • assets/narrative_template.md — fill-in-the-blank narrative structure: hook, situation, complication, resolution, call to action

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Rigorous A/B test statistical analysis. Use when analyzing experiment results, calculating statistical significance, checking for sample ratio mismatch, or validating test design before launch.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Track and document analytical assumptions and decisions. Use when making analytical choices, documenting trade-offs, ensuring transparency, or creating audit trails for analytical work.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Structured, reproducible analysis documentation. Use when documenting analysis findings, creating analysis notebooks, ensuring reproducibility, or building analysis archives for future reference.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Pre-delivery quality assurance for analysis work. Use when reviewing analysis before sharing with stakeholders, checking for completeness, validating assumptions, or ensuring clarity of recommendations.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

The English summary is being prepared. Showing the original description.

nimrodfisher/data-analytics-skills481Updated Sep 25, 2026

See all skills by nimrodfisher

Report a problem with this skill