data-storytelling
Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.
64
47%
Does it follow best practices?
Impact
94%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/business-analytics/skills/data-storytelling/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has a solid structure with an explicit 'Use when' clause that clearly communicates both purpose and trigger conditions. However, the capability description leans toward abstract concepts ('compelling narratives', 'persuasive structure') rather than concrete actions, and the trigger terms could be broader to capture more natural user language. The skill could also be more distinctive to avoid overlap with general visualization or presentation skills.
Suggestions
Replace abstract terms like 'compelling narratives' and 'persuasive structure' with concrete actions such as 'annotate charts with insights', 'write executive summaries', 'structure data-driven slide decks'.
Expand trigger terms to include common user language like 'dashboard', 'charts', 'graphs', 'KPIs', 'metrics', 'data insights', or 'board presentation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (data storytelling) and some actions ('visualization, context, and persuasive structure'), but the actions are somewhat abstract rather than concrete. It doesn't list specific operations like 'create charts', 'write narrative summaries', or 'build slide decks'. | 2 / 3 |
Completeness | Clearly answers both 'what' (transform data into compelling narratives using visualization, context, and persuasive structure) and 'when' (presenting analytics to stakeholders, creating data reports, building executive presentations) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'analytics', 'stakeholders', 'data reports', 'executive presentations', and 'visualization', but misses common variations users might say such as 'dashboard', 'charts', 'graphs', 'KPIs', 'metrics', 'data summary', or 'insights'. | 2 / 3 |
Distinctiveness Conflict Risk | The description could overlap with general data visualization skills, report generation skills, or presentation creation skills. While 'compelling narratives' and 'persuasive structure' add some distinctiveness, terms like 'data reports' and 'executive presentations' are broad enough to conflict with adjacent skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a comprehensive textbook chapter on data storytelling than a concise skill file for Claude. It explains many concepts Claude already knows (narrative arcs, transition phrases, do's and don'ts of presentations) and packs everything into one massive file. The concrete framework examples are its strongest asset, but the overall token cost is very high relative to the novel, actionable information provided.
Suggestions
Cut 60-70% of the content: remove 'Core Concepts' (Claude knows storytelling structure), 'Writing Techniques' (transition phrases, headline formulas), and 'Best Practices' (generic advice). Focus only on the specific frameworks and templates that define the expected output format.
Split into multiple files: keep SKILL.md as a brief overview with one example framework, then reference separate files like FRAMEWORKS.md, TEMPLATES.md, and VISUALIZATION.md for detailed content.
Add a concrete workflow with validation: e.g., '1. Identify the key insight, 2. Draft using a framework, 3. Verify all numbers are sourced and consistent, 4. Check that every slide/section advances the narrative, 5. Confirm a clear call-to-action exists.'
Replace ASCII art presentation mockups with actionable guidance on what tools/formats to actually produce (e.g., specific markdown structures, chart library code, or slide generation commands).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~300+ lines, mostly explaining concepts Claude already knows well (narrative structure, storytelling frameworks, writing techniques, transition phrases). The 'Core Concepts' section explains basic storytelling arcs, the 'Writing Techniques' section lists common transition phrases, and the 'Best Practices' are generic advice. Very little here is novel information Claude wouldn't already possess. | 1 / 3 |
Actionability | The frameworks provide concrete markdown templates and one executable Python matplotlib example, which is useful. However, most content is descriptive templates and placeholder visualizations (ASCII art boxes) rather than executable code or specific tool commands. The frameworks show structure but aren't truly copy-paste executable in most cases. | 2 / 3 |
Workflow Clarity | The frameworks provide a clear sequence (Hook → Context → Problem → Insight → Solution → Impact → CTA), and the slide templates show progression. However, there are no validation checkpoints, no feedback loops for iterating on the story, and no guidance on how to verify the narrative is effective or the data is correctly represented. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with everything inline. All frameworks, templates, visualization techniques, and writing tips are in a single file with no references to external files. The content would benefit enormously from splitting frameworks, templates, and visualization techniques into separate referenced files, keeping only a concise overview in the main skill. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.