Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/data-narrative-builder

@9449d36
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/data-narrative-builder

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈56 tokens for metadata: the name and description. ≈687 when used: this file. ≈2k more on demand in 3 files.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈223 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides guidelines and templates for building data-driven narratives. It consists entirely of static Markdown documentation and templates, with no executable code, network operations, or security risks detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/data-narrative-builder