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.
A well-built router skill: navigation is symptom-indexed and precise to the section level, with explicit conflict-resolution ordering and an unusually useful anti-rationalization table. Its main costs are token redundancy — the same routing map appears in four formats — and references to files that live outside this bundle, which limits verifiability.
Suggestions
Collapse the Quick Reference table, dot decision graph, and numbered Decision Tree into a single routing representation — the dot graph alone duplicates the table row-for-row at roughly 40 lines' cost.
Move version-specific details ("pre-iOS 26", "the 27 SDK ignores it on OS 27") into a short compatibility note under the relevant reference instead of inline in routing rows.
Trim Example Invocations to 2–3 genuinely ambiguous cases (e.g. the design vs accessibility overlap), since it currently repeats the routing table verbatim.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The same routing map is repeated four times — the Quick Reference table, the dot decision graph, the numbered Decision Tree, and Example Invocations all encode the identical symptom-to-file mapping (e.g. the alerts routing appears in every one). Version-specific details ("pre-iOS 26", "the 27 SDK", "OS 27") are embedded inline rather than isolated in a compatibility section, so the body is mostly efficient but has a clear tightening target — below anchor 4, yet far from anchor 2 since no concept explanations pad it. | 3 / 5 |
Actionability | Routing directives are concrete down to section level ("See `skills/sf-symbols-ref.md` (Part 11)", "`skills/hig.md` (quick answer) or `skills/hig-ref.md` (Alerts & Action Sheets, full rules)") and include environment fallbacks ("Elsewhere, search Axiom's skills for `skills/<agent>.md`"). It misses anchor 5 because the `sfsymbols` CLI and `/skill axiom-*` invocations are named without any usage example. | 4 / 5 |
Workflow Clarity | The routing sequence is unambiguous (symptom → reference) and Conflict Resolution supplies explicit ordering for overlapping cases ("Use design FIRST… Then use swiftui"), plus the anti-rationalization table counters common wrong turns. No validation checkpoints exist, but the skill is a read-only router so none are strictly required; it misses anchor 5 for having no verification step at all. | 4 / 5 |
Progressive Disclosure | The body is a pure symptom-indexed router pointing one level deep to clearly signaled files ("See `skills/hig.md`", "See `skills/liquid-glass-ref.md`"), which matches the ideal overview pattern. It falls short of anchor 5 because the referenced `skills/*.md` files are not present in this skill's bundle (no references/ or skills/ directory exists alongside SKILL.md) and several references point into sibling suites (axiom-swiftui's iphone-duo.md, axiom-media's carplay-hig.md), so the referenced paths cannot be verified within the bundle. | 4 / 5 |
Total | 15 / 20 Passed |