data-storytelling
Data Storytelling
| Property | Value |
|---|---|
| Domain | Data Analytics |
| Category | Narrative & Orchestration |
| Components | SKILL.md + data-storytelling.instructions.md + datastory.prompt.md |
| Depends | data-analysis (findings), data-visualization (charts), dashboard-design (layout) |
Overview
This is the orchestrator skill. It transforms raw data into a complete, coherent narrative by activating analysis, visualization, and dashboard skills in sequence. The output is a self-contained artifact -- typically an HTML dashboard or scrollable report -- where every chart, annotation, and KPI serves the story.
The cardinal rule: data stories have arguments, not just observations. A collection of charts with captions is a report. A data story says "here's what happened, here's why it matters, and here's what we should do."
Module 1: Three-Act Data Structure
Every data story follows this arc:
More from fabioc-aloha/alex_skill_mall
refactor
Systematic code refactoring to improve maintainability without changing behavior. Use when asked to "refactor this", "clean up this code", "improve code quality", "simplify this", "reduce complexity", or "eliminate code smells". Always preserves existing behavior.
1socratic-questioning
Help users discover answers, don't just deliver them.
1graphic-design
Patterns for visual design, SVG creation, layout composition, typography, and brand identity.
1deep-review
Adversarial code review with three parallel perspectives — Advocate, Skeptic, Architect — that create productive tension. Use for high-stakes PRs, architectural changes, or when single-pass review would miss issues. Surfaces findings through disagreement, not consensus.
1data-preparation
Data cleaning, profiling, transformation, and quality gates -- prepares raw data for visualization and analysis
1dashboard-design
Dashboard layout patterns, KPI card design, filter architecture, narrative flow through panels, and self-contained HTML generation
1