Conciseness

The routing table is dense and useful, but the ~20-line dot decision tree duplicates the Quick Reference table almost row-for-row, the bold 'You MUST use this skill for ANY macOS-specific development...' line re-states the frontmatter description, and version/time-sensitive markers ('OS27', '2026-272, 2026-289', 'iOS 27+') plus the two-line, content-free 'Cursor Subagent Routing' section add tokens without adding guidance. Not 4: the duplication is more than a minor instance; not 2: no concept explanations and the table is efficiently packed.

Actionability

Concrete, executable routing guidance: 'Another team's app or app group container access denied without a prompt (OS27)' → skills/sandbox-and-file-access.md, and 'Delegate to the touch-auditor subagent or /axiom-audit touch'. Minor gaps: bare WWDC/Tech Talk session numbers ('2026-272, 2026-289') with no titles or links, and partial doc paths ('/security/app-sandbox'). Not 5: those resource references are not directly usable; not 3: the guidance is specific and immediately actionable as routing, not vague or pseudocode.

Workflow Clarity

The single routing action (task area → reference file) is unambiguous via the symptom table and cross-suite rules ('Use axiom-macos for macOS-only concerns... Use axiom-swiftui for cross-platform SwiftUI'). Not 5: conflict resolution covers only 2 of the ~6 sibling suites, and 'Delegate to the appropriate Cursor subagent when this router calls for a specialized auditor' is stated yet only one table row ever calls for one; not 3: the routing sequence is clear and no destructive/batch operations exist to require validation checkpoints.

Progressive Disclosure

References are well-signaled and exactly one level deep (13 'See skills/*.md' routes in a scannable table), which matches the top anchor's structure — but none of the referenced files (skills/windows.md, skills/menus-and-commands.md, skills/touch.md, etc.) exist in the provided bundle; there is no references/, scripts/, assets/, or skills/ directory, so every navigation target is unresolvable. Not 4/5: the routing structure cannot be verified against actual files and the router points at missing files; not 2: nothing that belongs in separate files is inlined and the signaling is clear.

Specificity

Names the domain ('building ANY macOS app') and many concrete topic areas ('windows, menus, sandboxing, distribution, AppKit bridging or modernization (control events, state restoration, concentric corners), touch input'), but the only action verb is 'building' — it enumerates topics, not the specific actions of the anchor-4 pattern. Not 2: far more detailed than 'Processes PDF files'; not 4: no list of concrete actions the skill performs.

Completeness

The 'when' is explicit and highly specific ('Use when building ANY macOS app — windows, menus, sandboxing, distribution, ...'), with concrete trigger phrases; the 'what' is conveyed through the enumerated topic areas rather than an explicit capability statement. Not 5: what the skill actually does (reference material, routing, auditing) is never stated as an action; not 3: the 'when' is maximally explicit, not missing or weakly implied.

Trigger Term Quality

Good natural-term coverage — 'macOS app', 'windows', 'menus', 'sandboxing', 'distribution', 'AppKit', 'touch input', 'SwiftUI' are phrases users would actually say. A few natural terms are missing ('notarization', 'Developer ID', 'Catalyst', 'menu bar'), so it falls short of the comprehensive synonym coverage of the anchor-5 example. Not 3: coverage is well beyond 'some relevant keywords'.

Distinctiveness Conflict Risk

'macOS' is a clear niche with distinct triggers, and the qualifier 'macOS-specific SwiftUI patterns' attempts to delimit scope. Minor overlap risk remains with closely related sibling suites (the body itself acknowledges overlap with axiom-swiftui and axiom-security), so it does not reach the minimal-conflict anchor. Not 3: far more distinctive than 'Works with document files'.