Content
71%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 whose Anti-Rationalization table and cross-domain rules carry unusually high information density and whose progressive disclosure is exemplary. The main cost is token redundancy: the routing map is stated four times in different formats, and the subagent-routing section promises more than it delivers.
Suggestions
Consolidate the routing map: the Quick Reference table, dot decision tree, and numbered decision list repeat the same feature-to-file mapping; keep the table plus one tree and drop or merge the rest.
Remove or flesh out the 'Cursor Subagent Routing' section: name the available subagents and how to launch them, or fold the camera-auditor delegation into the decision list where it is already described.
Trim Example Invocations to only the ambiguous cases (multi-reference routing like iPhone Duo, or boundary cases like Apple Music library vs. playback), since most rows restate Quick Reference entries verbatim.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | There is no known-concept padding and rows carry dense, hard-won specifics (MusicKit request starvation, ScreenCaptureKit iOS-only filter constraints), but the same routing map is repeated four times — Quick Reference table, dot decision tree, numbered decision list, and Example Invocations — which could be consolidated into one or two representations. | 3 / 5 |
Actionability | Routing directives are concrete and executable ("Read: skills/camera-capture.md" with pattern and section numbers, "Launch camera-auditor agent") and include precise API-level guidance (SHManagedSession, AVDelegatingPlaybackCoordinator hostClockTime), but the "Cursor Subagent Routing" section is vague and near-empty, naming no subagents or launch mechanics beyond camera-auditor. | 4 / 5 |
Workflow Clarity | The decision tree and numbered list give a clear, unambiguous feature-to-reference sequence with explicit "stay here vs. invoke axiom-X" boundary rules for cross-domain cases. Not 5 because the subagent-delegation path is underspecified and validation checkpoints are N/A rather than addressed; not 3 because the sequence is coherent and complete for every listed feature. | 4 / 5 |
Progressive Disclosure | The body is a pure index/router: details are pushed into one-level-deep, clearly signaled `skills/*.md` references (with pattern/section pointers like "Pattern 8, deferred start"), cross-skill routes are explicitly named, and nothing that belongs in a reference file is inlined — an exemplar of clear overview navigation. | 5 / 5 |
Total | 16 / 20 Passed |