Content
56%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 well-organized router/index for 12 templates with a sensible selective-reading rule, but it is undermined by the fact that none of the referenced TEMPLATE.md files exist in the bundle, leaving the skill with no actual payload. Generic 'When to Use' and 'Limitations' boilerplate adds tokens without adding guidance.
Suggestions
Add the 12 referenced <template>/TEMPLATE.md files to the bundle, or remove/correct the broken links — as written, every disclosure path dead-ends at a nonexistent file.
Replace the vacuous 'When to Use' sentence and generic Limitations boilerplate with skill-specific guidance (e.g., what inputs to confirm, what to do when the user's stack isn't listed).
Add a fallback step to the Usage workflow for project types that match no template (e.g., pick the closest template or ask the user) so the routing never stalls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core content (the template table and the 4-step Usage) is lean, but the body carries vacuous boilerplate: 'This skill is applicable to execute the workflow or actions described in the overview' says nothing, and the generic Limitations section restates universal cautions. This matches 'mostly efficient but includes some unnecessary explanation'; not 4 because two full sections are padding that could be trimmed or made specific. | 3 / 5 |
Actionability | The Usage steps and the matching table give concrete routing guidance ('User says "create [type] app" → Match to appropriate template → Read ONLY that template's TEMPLATE.md'), but the final instruction 'Follow its tech stack and structure' is vague and the referenced payload files do not exist in the bundle, so the guidance cannot actually be executed. This lands at 'some concrete guidance but incomplete'; not 4 because the executable path dead-ends at missing files. | 3 / 5 |
Workflow Clarity | The routing workflow is a clear, correctly ordered 4-step sequence with an explicit selective-reading constraint, and the task is non-destructive so no validation checkpoints are required. Not 5 because there is no fallback step for when no template matches the user's request and no recovery guidance. | 4 / 5 |
Progressive Disclosure | The structure is well designed — a one-level-deep index table with clear 'When to Use' columns — but every one of the 12 referenced paths (e.g., nextjs-fullstack/TEMPLATE.md) is missing from the bundle, so navigation is broken in practice. Scored against the actual bundle structure this is 'some structure but could be better organized' rather than 4, since the disclosure chain points at files that do not exist. | 3 / 5 |
Total | 13 / 20 Passed |