data-story-outliner
Data Story Outliner - Auto-activating skill for Data Analytics. Triggers on: data story outliner, data story outliner Part of the Data Analytics skill category.
33
Quality
0%
Does it follow best practices?
Impact
97%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/data-story-outliner/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It only provides the skill name, a duplicate trigger term, and a category label without explaining what the skill does, what actions it performs, or when Claude should select it. The description fails on all dimensions and would be ineffective for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates structured outlines for data-driven narratives, identifies key insights for storytelling, organizes findings into compelling sequences').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to present data findings, create a data narrative, structure analytics insights, or build a story around metrics').
Add distinct file types, contexts, or scenarios to differentiate from other analytics skills (e.g., 'for transforming raw analysis into executive presentations or stakeholder reports').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Data Story Outliner') and its category ('Data Analytics') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating outlines, structuring narratives, analyzing data, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. There is no 'Use when...' clause or equivalent trigger guidance. Both the what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data story outliner' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing natural terms like 'outline', 'narrative', 'data presentation', 'story structure', 'insights summary', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The generic 'Data Analytics skill category' label could conflict with many other data-related skills. Without specific capabilities or use cases defined, there's no clear niche to distinguish this from other analytics or storytelling skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It describes what a data story outliner skill would do without providing any actual guidance, examples, frameworks, or actionable instructions for creating data story outlines. The entire content could be replaced with a single sentence without losing information.
Suggestions
Add a concrete data story outline framework or template (e.g., Context → Insight → Action structure) with specific sections and what each should contain
Include at least one worked example showing how to transform raw data findings into a narrative outline
Provide specific guidance on visualization selection, narrative flow, and audience considerations for data stories
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, examples, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually outline a data story. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for creating a data story outline. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, examples, or templates. The content is both shallow and poorly organized. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.