Content
67%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-designed language router: lean, concrete, and clearly sequenced, with a sensible default and a strong read-before-code gate. Its critical flaw is structural — both referenced skill files are absent from the bundle, so progressive disclosure fails at the first hop.
Suggestions
Ship ts/skill.md and py/skill.md alongside SKILL.md — both routing targets the body instructs Claude to read are missing, leaving the router pointing at nothing.
Extend the Step 1 table with a precedence rule for conflicting signals (e.g., the user mentions both TypeScript and Python), mirroring the existing 'No clear signal → TypeScript' default.
De-duplicate the TypeScript-default rule and the MUST-read instruction (each is stated twice); one statement of each is sufficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line router body is lean and assumes Claude's competence (no concept explanations, no padding), but the TypeScript default is stated twice (paragraph and table row) and the ⚠️ paragraph repeats Step 2's read-the-file instruction. Efficient overall — these are minor instances that could be trimmed, keeping it below a 5. | 4 / 5 |
Actionability | Concrete, executable routing guidance: an exact signal-to-language table, an explicit default rule, and precise file paths (ts/skill.md, py/skill.md) with a MUST-read gate. Not a 5 because the primary routing targets are missing from the bundle (verified: neither ts/skill.md nor py/skill.md exists), so the guidance cannot actually be executed as shipped here; not a 3 because what is written is specific and unambiguous rather than pseudocode. | 4 / 5 |
Workflow Clarity | Steps 1–2 are clearly sequenced with an explicit default and a hard checkpoint ("Do NOT proceed with any code generation until you have read it"), appropriate for a single-purpose routing skill. Minor gaps: the conflicting-signals case (user mentions both TypeScript and Python) has no precedence rule, and no fallback is given for a missing ts/py file (only for sibling skills). | 4 / 5 |
Progressive Disclosure | The design intent is correct — a lean router pointing one level deep to per-language skill files — but the actual bundle contains no references/, scripts/, or assets/ directories, and neither referenced path (ts/skill.md, py/skill.md) exists, so the router points at nothing. Scored against the actual bundle structure per the guidelines; the missing targets leave disclosure broken in practice despite the clear signaling, which is worse than the "references present but not clearly signaled" anchor at 3. | 2 / 5 |
Total | 14 / 20 Passed |