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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill data-story-outlinerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It only provides the skill name and category without explaining what the skill does, when to use it, or any natural trigger terms. The description would be completely ineffective for skill selection among multiple options.
Suggestions
Add specific actions the skill performs (e.g., 'Creates structured outlines for data narratives, identifies key insights, organizes findings into compelling story arcs')
Add a 'Use when...' clause with natural trigger terms like 'data story', 'presentation outline', 'narrative structure', 'communicate findings', 'data insights summary'
Include the types of inputs/outputs (e.g., 'Takes raw analysis results and produces structured outlines for reports, presentations, or stakeholder communications')
| 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, and the capabilities are completely unstated. | 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 description is extremely generic - 'Data Analytics skill category' could apply to dozens of different skills. Without specific capabilities or triggers, this would easily conflict with any other data-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what a data story outliner skill would do without providing any actual guidance, examples, frameworks, or steps for outlining data stories. The entire content could be replaced with a single sentence and lose nothing of value.
Suggestions
Add a concrete framework or template for data story outlines (e.g., situation-complication-resolution, or a numbered structure with specific sections like 'Key Finding', 'Supporting Data', 'Recommendation')
Include at least one complete example showing input data context and the resulting story outline structure
Provide specific guidance on how to identify the narrative arc from data (what questions to ask, how to prioritize findings)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual 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, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually outline a data story or provides any executable examples. | 1 / 3 |
Workflow Clarity | No workflow 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 | The content is a flat, uninformative structure with no references to detailed materials, examples, or templates. There's nothing to progressively disclose because there's no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.