Content
73%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.
A well-structured router skill: routing is unambiguous, conflicts between sibling skills are resolved explicitly, and references are clearly signaled one level deep. The main cost is redundancy — the same routing table appears in three forms plus a worked-examples section — which inflates token cost without adding navigational value.
Suggestions
Collapse the routing to two forms maximum: keep the Quick Reference table and the numbered Decision Tree, and delete the dot graph, which duplicates the numbered list almost entry-for-entry.
Trim or remove the "Critical Patterns" section — it re-summarizes the contents of files the reader is about to open; the Quick Reference one-liners already set expectations.
Cut "Example Invocations" to 3–4 representative cases or fold the user phrasings into the Quick Reference table's symptom column.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The routing table, dot-graph decision tree, and numbered Decision Tree section encode the same task→file mapping three times, and "Example Invocations" restates the Quick Reference entries. Not 2 because there is no padding that explains concepts Claude already knows — the waste is duplication, not verbosity — but clear tightening opportunities remain. | 3 / 5 |
Actionability | As an instruction-only router, every entry gives a concrete directive ("Read `skills/hig.md`", "→ `/skill axiom-swiftui`") and the Example Invocations map real user phrasings to specific files. Not 5 because some entries defer to other suites (axiom-payments, axiom-swiftui) without a path, and no inline fallback exists if a referenced file is unavailable. | 4 / 5 |
Workflow Clarity | The single action — route a design question to the correct reference — is unambiguous via the numbered decision tree and the Conflict Resolution section's explicit ordering ("Use design FIRST... Then use swiftui"). No destructive or batch operations exist, so no validation checkpoints are required; the simple-skill exception applies. | 5 / 5 |
Progressive Disclosure | The body is a genuine overview with clearly signaled, one-level-deep references (`skills/hig.md`, `skills/liquid-glass.md`, `skills/sf-symbols.md`, etc.) mapped by symptom in the Quick Reference table. Not 5 because the "Critical Patterns" section re-summarizes each referenced file's contents inline and the dot graph duplicates the numbered routing list, adding bulk that belongs at the reference layer. | 4 / 5 |
Total | 16 / 20 Passed |