CtrlK
BlogDocsLog inGet started
Tessl Logo

data-storytelling

Transform raw data into compelling narratives that drive decisions and inspire action.

48

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/data-storytelling/SKILL.md

The canonical home for this skill is data-storytelling in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

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

The skill is rich with concrete, ready-to-adapt templates and a usable matplotlib example, making it genuinely actionable. Its weaknesses are a monolithic structure with a broken reference file and a vague top-level workflow that lacks explicit validation guidance.

Suggestions

Move the full framework templates, presentation templates, and visualization techniques into separate reference files under references/ and link to them one level deep, keeping SKILL.md a concise overview.

Fix or remove the broken `resources/implementation-playbook.md` reference — the directory does not exist; either create the file under references/ or drop the pointer.

Replace the generic "Instructions" boilerplate with a concrete, sequenced workflow (e.g., identify the audience and decision → pick a framework → draft the headline insight → validate the claim against the data → assemble the narrative) with an explicit verify step.

DimensionReasoningScore

Conciseness

The body is mostly actionable templates rather than concept-explanation padding, but at ~460 lines with bulky ASCII art templates and generic boilerplate ("Apply relevant best practices and validate outcomes"), it could be tightened.

3 / 5

Actionability

Provides concrete frameworks with specific numbers, a working matplotlib annotation example, and copy-paste template structures; minor gaps include undefined variables in the code and templates that need filling in.

4 / 5

Workflow Clarity

The narrative arc and template flows give a recognizable sequence, but the actual "Instructions" workflow is vague boilerplate ("Apply relevant best practices and validate outcomes") with no concrete validation checkpoints.

3 / 5

Progressive Disclosure

Content is monolithic — full framework templates, presentation templates, and writing techniques are all inlined in one ~460-line file, and the sole reference (`resources/implementation-playbook.md`) is broken (no such file or directory exists).

2 / 5

Total

12

/

20

Passed

Description

48%Weight 40%Scale 1-5

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 states a clear purpose and distinct niche but stops short of listing concrete capabilities or providing explicit "use when" trigger guidance, relying on outcome-fluff ("drive decisions and inspire action") instead. It is a competent but incomplete description.

Suggestions

Enumerate concrete actions (e.g., structure insights as a story arc, design executive-ready slide narratives, annotate charts to highlight the key finding) instead of stopping at one composite action.

Add an explicit "Use when..." clause with natural trigger terms such as presenting analytics to executives, building investor or QBR decks, or turning analysis into a recommendation.

Replace benefit buzzwords ("drive decisions and inspire action") with capability language so the description reads as a capability list rather than a tagline.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Transform raw data into compelling narratives"), but "drive decisions and inspire action" are outcomes/buzzwords rather than enumerated capabilities, leaving actions minimal.

2 / 5

Completeness

Has a clear "what" (transform data into narratives) but no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes relevant keywords "raw data" and "narratives", but misses the most natural trigger terms users would say ("story", "storytelling", "presentation", "data story").

3 / 5

Distinctiveness Conflict Risk

The data-to-narrative framing carves a fairly distinct niche with only minor overlap risk against generic presentation or business-writing skills.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.