Content
63%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 skill body is well-structured and concise as a router to per-stack templates, but its references point to TEMPLATE.md files that are absent, leaving it non-actionable and its progressive disclosure unfulfilled.
Suggestions
Ship the referenced bundle files (e.g. nextjs-fullstack/TEMPLATE.md, express-api/TEMPLATE.md) so the navigation actually resolves.
Replace the empty 'When to Use' filler line with a concrete trigger that names the project types, or remove it since the description already covers 'when'.
Add a brief fallback note on what a TEMPLATE.md contains (structure/tech-stack guidance) so the skill remains useful even before a template is opened.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean: a short overview, a compact selection table, and a 4-step usage list, with only minor filler such as the redundant blockquote and the vacuous 'When to Use' line ('applicable to execute the workflow or actions described in the overview'). | 4 / 5 |
Actionability | It gives a concrete selection workflow (match project type -> read that template's TEMPLATE.md) but delegates all real executable content to TEMPLATE.md files that do not exist, so the guidance is incomplete and not directly executable. | 3 / 5 |
Workflow Clarity | The four-step Usage sequence is clear and well-ordered for a non-destructive scaffolding task; no validation checkpoints are required for creating new projects, but the steps are thin enough to stay at 4 rather than 5. | 4 / 5 |
Progressive Disclosure | The design is a clean overview pointing one level deep to 12 separate TEMPLATE.md files, but those files (and the references/scripts/assets bundle dirs) do not exist, so the references are dangling rather than materialized. | 3 / 5 |
Total | 14 / 20 Passed |