Content
85%Reviews 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 with actionable routing logic, clear workflow sequencing, and clean progressive disclosure. Its main weakness is verbosity in the enforcement/Red Flags prose, which lectures Claude beyond what the routing guidance needs.
Suggestions
Collapse the EXTREMELY-IMPORTANT block and the Red Flags table into a single concise 'Always check for a matching Axiom skill before responding to iOS/Swift tasks; when in doubt, check first' rule — the repetitive 'not negotiable / not optional / cannot rationalize' phrasing is padding Claude does not need.
Trim the Red Flags table entries that merely restate the Rule (e.g. 'I remember how to do this from last time', 'I'll gather info first, then check skills') to the few that add non-obvious domain-specific signal.
Move the Device Hub version notes (Xcode 26 vs 27, 'iOS 26 at WWDC 2025') into the referenced device-control-ref.md or a clearly marked version section so time-sensitive detail does not inflate the router overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The routing table, priority list and detection criteria are efficient, but the EXTREMELY-IMPORTANT block ('This is not negotiable. This is not optional. You cannot rationalize your way out of this.') and the redundant Red Flags table pad the body with motivational repetition Claude does not need — 'mostly efficient but could be tightened' rather than fully lean. | 2 / 3 |
Actionability | It gives concrete, copy-paste-ready guidance: a trigger-to-file routing table, copy-paste commands ('/skill axiom-concurrency', '/axiom:fix-build'), explicit detection rules (.xcodeproj/.xcworkspace), and worked multi-domain examples — specific rather than vague despite being an instruction-only router. | 3 / 3 |
Workflow Clarity | The routing workflow is clearly sequenced — detect via iOS project criteria, apply the numbered skill priority, invoke router(s), follow the specialized skill — with the priority list and multi-domain rules acting as decision checklists; no destructive/batch step is present that would require a validate-fix-retry loop. | 3 / 3 |
Progressive Disclosure | The body is a clean overview that routes to one-level-deep, well-signaled references (skills/*-ref.md) via a navigation table, splitting detail appropriately; the referenced files are suite-sibling skills rather than local bundle files, which is the intended router pattern, so structure matches the score-3 anchor. | 3 / 3 |
Total | 11 / 12 Passed |