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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured with excellent progressive disclosure and a real one-level reference, but the main body restate common narrative concepts and stays abstract, deferring concrete worked examples to the bundled file. Workflows lack explicit checkpoints.

Suggestions

Trim or collapse the Setup->Conflict->Resolution and narrative-arc blocks, which restate concepts Claude already knows, into a single compact reference or move them to details.md.

Add one small concrete worked example (e.g., a sample insight headline + supporting metric) directly in the body so the top tier is actionable without loading the reference.

Add a light validation/checkpoint step to the narrative process, such as 'verify each insight maps to a specific metric and a recommended action', to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with compact tables and terse bullet lists, but the Setup->Conflict->Resolution and six-step narrative-arc blocks restate widely known storytelling concepts Claude already understands.	2 / 3
Actionability	Do's and Don'ts give some concrete directives ('Start with the so what', 'Use the rule of three'), but the main body stays fairly abstract and defers all worked examples to the reference file rather than providing specific, copy-ready guidance inline.	2 / 3
Workflow Clarity	A sequence exists (the six-step narrative arc) and 'When to Use' scopes the task, but there are no explicit checkpoints or feedback loops; for an advisory skill this is acceptable yet not a clearly validated workflow.	2 / 3
Progressive Disclosure	The body is a clear overview with a single, well-signaled one-level-deep reference ('Detailed pattern documentation lives in references/details.md'), and that referenced file genuinely exists, matching the score-3 anchor.	3 / 3
	Total	9 / 12 Passed

Description

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 covers both what the skill does and when to use it with a clear 'Use when' trigger, but leans on somewhat abstract language that limits specificity and distinctiveness. Trigger terms are natural but lack breadth of variations.

Suggestions

Replace abstract phrasing like 'compelling narratives' and 'persuasive structure' with concrete actions (e.g., 'structure insights as setup-conflict-resolution, choose chart types, draft headlines with quantified impact').

Broaden trigger terms to cover common variations users would say, such as 'data reports', 'executive presentations', 'quarterly business reviews', 'investor decks', and 'analyst updates'.

Sharpen the niche to reduce overlap with generic presentation skills, e.g., anchoring on 'data-driven decision narratives for non-technical stakeholders'.

Dimension	Reasoning	Score
Specificity	Names the domain and several action areas ('visualization, context, and persuasive structure') but phrases like 'compelling narratives' are abstract rather than the multiple concrete actions the score-3 anchor requires.	2 / 3
Completeness	Explicitly answers both what ('Transform data into compelling narratives...') and when ('Use when presenting analytics...'), matching the score-3 anchor with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Includes natural user phrases ('presenting analytics to stakeholders, creating data reports, building executive presentations') but offers limited variations compared to the broad term coverage of the score-3 anchor.	2 / 3
Distinctiveness Conflict Risk	The stakeholder/analytics niche is somewhat specific, but generic phrasing ('compelling narratives', 'persuasive structure') means it could overlap with general presentation or report-writing skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: d7cf7dc

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.