Content
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but excessively verbose framework document that reads more like a tutorial or design document than an efficient skill instruction. It explains many concepts Claude already understands (task decomposition principles, capability taxonomies) and includes extensive placeholder-heavy templates inline rather than in separate reference files. The core actionable content — use `npx skills find` to search, decompose tasks, create skills when gaps exist — could be conveyed in a fraction of the space.
Suggestions
Reduce content by 60-70%: Remove the Universal Capability Types table, Task Decomposition Principles section, and elaborate ASCII output format template — Claude already knows these concepts and can generate appropriate formats.
Extract the skill creation template, output format template, and capability taxonomy into separate reference files (e.g., TEMPLATE.md, OUTPUT_FORMAT.md, CAPABILITIES.md) and reference them from the main SKILL.md.
Add explicit validation/error-handling steps: What to do when `npx skills find` returns no results, when skill installation fails, or when a created skill doesn't work as expected — include concrete recovery commands.
Replace placeholder YAML examples with one complete, realistic end-to-end example that shows actual skill names and real commands rather than '{task name}' and '{capability_type}' placeholders.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. The 'Universal Capability Types' table, task decomposition principles, elaborate ASCII output format templates, and multiple full YAML examples are largely things Claude already knows how to do. The skill explains basic concepts like atomicity, single responsibility, and independence that don't need teaching. Much of this could be condensed to ~80 lines. | 1 / 3 |
Actionability | The skill provides concrete CLI commands (npx skills find, npx skills add, npx skills init) and structured YAML examples, which is good. However, much of the content is template/placeholder-heavy rather than truly executable — the YAML blocks use placeholder syntax like '{task name}' and the workflow is more of a conceptual framework than copy-paste-ready instructions. | 2 / 3 |
Workflow Clarity | The six phases are clearly sequenced and the overall flow is logical. However, validation checkpoints are weak — the 'verification' section in the execution plan template is just placeholders, and there are no explicit feedback loops for error recovery (e.g., what to do if skill search fails, if skill installation fails, or if a created skill doesn't work). The 'Handle errors gracefully' best practice is vague. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files and no references to external files. The capability taxonomy table, skill template, output format template, and multiple full examples are all inline when they could be split into separate reference files. The content would benefit enormously from splitting into overview + reference files. | 1 / 3 |
Total | 6 / 12 Passed |