Content
60%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 genuinely actionable router: concrete commands, an environment-first diagnostics procedure with explicit validation checkpoints, and clearly signaled one-level-deep routing to sub-skills. Its main defect is heavy redundancy — the same routing table appears three times (Routing Logic, Decision Tree, Example Invocations) — which costs significant tokens without adding guidance, and small structural flaws (misordered section numbers 16/15) further suggest it needs tightening.
Suggestions
Collapse the redundancy: keep the Routing Logic subsections as the canonical map and replace the Decision Tree and the ~40-entry Example Invocations list with a handful of representative examples, cutting the file roughly in half.
Fix structural jumbles: renumber sections so code-signing (15) precedes xclog-ref (16) as listed, and move the dense axbuild/pgrep diagnostics procedure into a referenced file (e.g. scripts/axbuild.md) so SKILL.md stays a lean router overview.
Make the build/test code block executable by showing how to discover the scheme and destination inline (e.g. `xcodebuild -list` / `xcrun simctl list`) before the "$AXBUILD" invocation, instead of leaving $SCHEME/$DESTINATION/$PACKAGE as undefined placeholders.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The routing map is restated three times: "Routing Logic" (16 subsections with triggers), the "Decision Tree" (16 lines repeating the same mapping), and ~115 lines of "Example Invocations", plus a "When to Use" list duplicating the description. This matches anchor 2 (several unnecessary/padded sections) — not 3 because the duplication is substantial rather than occasional, not 1 because there is no padding that explains concepts Claude already knows. | 2 / 5 |
Actionability | Concrete, executable guidance throughout: `pgrep -lx xcodebuild; echo "pgrep exit=$?"`, the `"$AXBUILD" xcodebuild -scheme "$SCHEME" -destination "$DESTINATION" build` block, slash commands (`/axiom:fix-build`, `/axiom:console`), and explicit skill file paths. Matches anchor 4 — not 5 because the code block uses undefined placeholder variables ($SCHEME, $DESTINATION, $PACKAGE) and is not copy-paste ready, though the text does instruct discovering the actual scheme and destination first. | 4 / 5 |
Workflow Clarity | The "Capture Build and Test Diagnostics" sequence is clearly ordered with explicit checkpoints: pgrep exit-code interpretation ("exit 1 means none are running"), "Inspect `command` (native outcome) and `collection` (evidence completeness) separately", "record its exit status", and truncation-marker checks before rebuilding. Matches anchor 4 — not 5 because document-level organization (sections numbered 14→16→15, an interleaved auto-maintained block, and three parallel routing restatements) muddies the overall flow; not 3 because validation checkpoints are explicit rather than implicit. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent); routing pointers such as "Invoke: `skills/xcode-debugging.md`" and "See axiom-shipping (skills/testflight-triage.md)" are one level deep and clearly signaled, an appropriate split for a router. Matches anchor 4 — not 5 because the ~115-line Example Invocations list and the dense diagnostics procedure inflate the main file where a separate reference would serve, and section ordering is jumbled; not 3 because references are clearly signaled and content is mostly well placed. | 4 / 5 |
Total | 14 / 20 Passed |