lyndonkl/visual-storytelling-design
skills/visual-storytelling-design/SKILL.md
Transforms data into compelling visual narratives by applying narrative structure, annotation techniques, scrollytelling patterns, and honest framing to data journalism, presentations, and infographics. Use when creating data-driven articles or reports, designing infographics with narrative, building scrollytelling experiences, annotating charts to guide interpretation, or when user mentions data storytelling, presentation design, annotated chart, narrative visualization.
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude visual-storytelling-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:25 AM161.1s4 files scanned
SKILL.md
- name:
- visual-storytelling-design
- description:
- Transforms data into compelling visual narratives by applying narrative structure, annotation techniques, scrollytelling patterns, and honest framing to data journalism, presentations, and infographics. Use when creating data-driven articles or reports, designing infographics with narrative, building scrollytelling experiences, annotating charts to guide interpretation, or when user mentions data storytelling, presentation design, annotated chart, narrative visualization.
Visual Storytelling Design
Table of Contents
- Story Design Workflow
- Path Selection Menu
- Path 1: Build Narrative Structure
- Path 2: Master Annotation
- Path 3: Design Scrollytelling
- Path 4: Apply Framing & Metaphors
- Quick Reference
- Guardrails
Core principle: Structuring data as narrative (Context → Problem → Evidence → Insight) aids comprehension and retention. Annotations guide attention, progressive disclosure reveals complexity gradually, and framing provides context for accurate interpretation.
Related skills: Use cognitive-design for cognitive principles, d3-visualization for D3.js implementation, design-evaluation-audit for systematic evaluation, cognitive-fallacies-guard for integrity checks.
Story Design Workflow
Time: 1-2 hours
Copy this checklist and track your progress:
Story Design Progress:
- [ ] Step 1: Define Narrative
- [ ] Step 2: Choose Structure
- [ ] Step 3: Apply Cognitive Techniques
- [ ] Step 4: Review for Clarity & Integrity
Step 1: Define Narrative
Determine the story arc: What's the context? What's the question/problem? What data answers it? What's the insight? Choose an opening strategy: lead with human impact, surprising finding, or visual.
Resource: Narrative Techniques — Narrative Structure section
Step 2: Choose Structure
Select a template and pattern that fits your story type, audience, and medium. Options include step-by-step article, magazine style, annotated chart, interactive exploration, or presentation deck.
Resource: Storytelling Patterns — Templates and Decision Matrix
Step 3: Apply Cognitive Techniques
Add annotations (callouts, arrows, shaded regions, direct labels). Apply framing with baselines, comparisons, and denominator clarity. Use scrollytelling for progressive revelation if web-based. Consider visual metaphors.
Resource: Narrative Techniques — Annotations, Scrollytelling, Framing sections
Step 4: Review for Clarity & Integrity
Verify the story is honest (no cherry-picking, balanced framing), clear (insight obvious in 5 seconds), and complete (sources cited, limitations noted). Use design-evaluation-audit for systematic evaluation and cognitive-fallacies-guard for integrity verification.
Path Selection Menu
Path 1: Build Narrative Structure
Choose this when: Starting a data story and need to define the narrative arc and opening strategy.
→ Go to Narrative Techniques — Sections 1-2
Path 2: Master Annotation
Choose this when: Adding annotations to guide interpretation of existing charts and visualizations.
→ Go to Narrative Techniques — Section 3
Path 3: Design Scrollytelling
Choose this when: Building web-based progressive revelation experiences.
→ Go to Narrative Techniques — Section 4
Path 4: Apply Framing & Metaphors
Choose this when: Providing context, baselines, comparisons, and visual metaphors.
→ Go to Narrative Techniques — Sections 5-6
Quick Reference
5 Storytelling Principles
- Lead with insight, not topic — Title: "Remote workers report 23% higher satisfaction" not "Remote work survey results"
- Annotate the insight — Don't make readers discover it; point it out with callouts
- Provide context — Baselines, historical comparisons, denominators for every percentage
- One change at a time — Scrollytelling: highlight OR annotate, not both simultaneously
- Be honest — Show full data, acknowledge limitations, avoid cherry-picking
Guardrails
Scope: This skill provides narrative structure, annotation techniques, scrollytelling patterns, framing guidance, story templates, and quality checklists for data storytelling. It does not implement code, evaluate general usability, teach cognitive theory, or check for misleading patterns.
Related Skills
lyndonkl/skills/zettel-note
development
VerifiedTrustedCommunity
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-transfer-planner
development
VerifiedTrustedCommunity
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-tournament-state
testing
VerifiedTrustedCommunity
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-signal-emitter
development
VerifiedTrustedCommunity
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.
119SKILL.mdUpdated Jun 12, 2026