Content
85%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 body: concrete routing with exact file destinations, an unambiguous decision tree, and clean one-level-deep progressive disclosure to nine subskill files. Its one weakness is redundancy — the same routing table is effectively restated in the When to Use list, the Decision Tree, and the Example Invocations, which inflates token cost without adding new routing information.
Suggestions
Consolidate the three overlapping routing mechanisms: keep the Decision Tree and a small set of Example Invocations, and fold the "When to Use" bullet list into them, since all three state the same query-to-file mappings (e.g. the ProMotion 60fps case appears in all three sections).
Trim the "Critical Patterns" section, which duplicates the per-file bullet summaries already given under "Routing Logic" (e.g. MTKView/60fps defaults appear in both the display-performance routing bullets and its Critical Patterns entry).
Consider pruning the Example Invocations list to only cases not already covered verbatim by the Decision Tree (e.g. "Setting up MTKView for the first time" vs. decision-tree item 4), keeping one representative example per subskill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The routing mapping is repeated three times in parallel forms — "When to Use" (19 bullets), "Decision Tree" (21 items), and "Example Invocations" (24 examples); e.g. the ProMotion/60fps case appears in all three plus the Anti-Rationalization table. There is no concept over-explanation, but the duplication is noticeable and could be tightened into one mechanism plus examples, so it sits between anchors 2 and 3. | 3 / 5 |
Actionability | Concrete, fully actionable router guidance: exact file destinations per symptom ("→ See skills/resizable-rendering.md", "metal-migration-ref (Part 6)"), an Anti-Rationalization table with specific corrections, and 24 realistic user queries each mapped to an exact file. Instruction-only guidance without code, but complete. | 5 / 5 |
Workflow Clarity | A router's single action (match query → read the named subskill file) is unambiguous: the 21-item Decision Tree covers the common cases with clear destinations, and all three routing mechanisms (When to Use, Decision Tree, Example Invocations) agree with each other, leaving no conflicting guidance. | 5 / 5 |
Progressive Disclosure | Clear overview router with well-signaled, one-level-deep references: nine subskill files, each introduced with a "→ See skills/..." pointer plus a short bullet list of its contents, and no nested references. Note: no bundle files (skills/, references/) are present in the reviewed directory, so referenced paths could not be verified against an actual bundle; scored on the body's structure, which matches the exemplary anchor. | 5 / 5 |
Total | 18 / 20 Passed |