Content
100%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.
An exemplary router SKILL.md: lean shared context full of exact tool specifics, an unambiguous direction-picking workflow with an explicit ambiguity checkpoint, and well-signaled one-level-deep references that check out against the actual bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | A ~30-line router containing exclusively non-obvious knowledge (tool arguments, URL→fileKey/nodeId parsing, SF Symbol round-trip rules, sibling-skill load order) with zero explanation of concepts Claude already knows; the only candidate trim is the References table, which lightly duplicates the direction table's links. | 5 / 5 |
Actionability | Copy-paste-ready instructions rather than pseudocode: 'Pass clientLanguages: "swift" and clientFrameworks: "swiftui"', 'replace - with : in nodeId', 'call figma.util.getSfSymbolCharacter(name) inside use_figma', plus exact semantic-color mappings. Per the instruction-only note, the absence of code blocks is not penalized when guidance is this concrete. | 5 / 5 |
Workflow Clarity | The routing action is unambiguous: a decision table mapping triggers to references plus an explicit disambiguation checkpoint — 'If the request is ambiguous… ask the user which direction before loading a reference'. As a single-purpose router with no destructive or batch operations, the simple-skill exception applies. | 5 / 5 |
Progressive Disclosure | The body defers all direction-specific detail to references/design-to-code.md and references/code-to-design.md — both real, substantive files (273 and 167 lines) in the bundle — one level deep, each linked with explicit when-to-load conditions. Verified against the actual bundle structure. | 5 / 5 |
Total | 20 / 20 Passed |