Content
56%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-architected router with explicit routes, a decision tree, and genuinely useful anti-rationalization and conflict-resolution sections, plus concrete diagnostic commands. However, roughly a third of the body is redundant restatement of the routing table, and every referenced detail file is missing from the bundle, leaving the progressive-disclosure structure unverifiable.
Suggestions
Delete or drastically trim the ~120-line 'Example Invocations' section — it restates the Routing Logic triggers one-for-one — and let the Routing Logic and Decision Tree carry the mapping once each.
Fix the disordered section numbering (16 'xclog-ref' appears before 15 'code-signing') and deduplicate guidance stated twice, such as the code-signing 'never code bugs' rationale in section 15 and the Anti-Rationalization table.
Ship the referenced detail files (skills/xcode-debugging.md, skills/build-performance.md, skills/lldb.md, etc.) in the bundle or correct the paths, since the skill currently references files that do not exist alongside it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 458-line body restates the same trigger-to-route mapping four times — 'When to Use', 'Routing Logic', 'Decision Tree', and a ~120-line 'Example Invocations' section — and the code-signing 'never code bugs' rationale appears in both section 15 and the Anti-Rationalization table. This is noticeably verbose with several padded, redundant sections, beyond the 'could be tightened' level of score 3. | 2 / 5 |
Actionability | Routes carry concrete invoke targets ('skills/xcode-debugging.md', named agents, slash commands) and the diagnostics section gives executable checks like 'command -v axbuild' and 'pgrep -lx xcodebuild'. Not score 5 because the build block relies on unresolved $SCHEME/$DESTINATION variables and some prose guidance ('Discover the actual scheme and destination') lacks the specific step. | 4 / 5 |
Workflow Clarity | The decision tree gives a clear numbered routing sequence, and the diagnostics section has real checkpoints (pgrep exit-code interpretation, 'Read an existing log before considering another build', saved-log fallback). Not score 5 due to disordered section numbering (16 appears before 15) and the absence of any route-match verification step. | 4 / 5 |
Progressive Disclosure | The thin-router-pointing-to-detail-files architecture is the right progressive-disclosure design and every path is clearly signaled, but the bundle contains zero files — none of the referenced skills/*.md targets (e.g. skills/xcode-debugging.md, axiom-shipping's testflight-triage.md) exist alongside SKILL.md, so the split is unverified and the references dangle. This fits 'references present but the organization cannot be confirmed' better than score 4's 'minor organization gaps'. | 3 / 5 |
Total | 13 / 20 Passed |