Content
25%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a facade: generic placeholder instructions, duplicated trigger lists, an empty heading, and a link catalog pointing entirely at non-existent files. A reader following any reference fails, and nothing in the body conveys actual data-storytelling technique.
Suggestions
Fix progressive_disclosure first: either add the referenced sub-skills files and resources/implementation-playbook.md to the bundle, or remove the broken links and inline the essential framework/technique guidance directly in SKILL.md.
Replace the boilerplate Instructions ("Apply relevant best practices and validate outcomes") with concrete, domain-specific steps, e.g., how to pick a story framework (problem-solution, trend, comparison), structure an executive summary slide, or write a headline from a chart finding.
Remove the tautological "Do not use this skill when" bullets, the empty "## Core Concepts" heading, and the "Use this skill when" list that duplicates the frontmatter description to reduce token waste.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Several sections are pure padding: the tautological "Do not use this skill when" bullets ("The task is unrelated to data storytelling"), an empty "## Core Concepts" heading, and a "Use this skill when" list that duplicates the frontmatter description. This is noticeably below 'mostly efficient' (anchor 3), though it never devolves into explaining concepts Claude already knows (anchor 1). | 2 / 5 |
Actionability | The Instructions are generic boilerplate ("Apply relevant best practices and validate outcomes") with no domain-specific guidance, and the only concrete pointer ("open resources/implementation-playbook.md") targets a file that does not exist. Scored 2 rather than 1 only because the 19 module link titles (e.g., "Framework 1: The Problem-Solution Story", "Headlines That Work") act as high-level hints of what is covered. | 2 / 5 |
Workflow Clarity | A rough sequence exists ("Clarify goals, constraints, and required inputs" → "Apply relevant best practices" → "Provide actionable steps and verification") but the steps are generic and poorly defined, and validation is merely asserted ("validate outcomes") with no checkpoint or feedback loop — matching anchor 2. | 2 / 5 |
Progressive Disclosure | All 20 referenced paths — "resources/implementation-playbook.md" and the 19 "./sub-skills/*.md" links — point to files that do not exist in the bundle, making navigation effectively broken; additionally the "Core Concepts" section is empty and the reference roots are inconsistent ("resources/" vs "./sub-skills/"). The SKILL.md itself has section structure, keeping it above anchor 1. | 2 / 5 |
Total | 8 / 20 Passed |