CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-build

Use when ANY iOS build fails, test crashes, Xcode misbehaves, or environment issue occurs before debugging code. Covers build failures, compilation errors, dependency conflicts, simulator problems, environment-first diagnostics.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured router: highly actionable with concrete invoke targets, a clear decision tree, and one-level-deep references to sibling skills. The main weakness is conciseness — the large 'Example Invocations' section duplicates the routing triggers and could be cut or condensed.

Suggestions

Cut or heavily condense the 'Example Invocations' section (lines 317-435): its user-phrasing examples already appear as triggers in 'Routing Logic', so keeping both doubles the token cost with little added routing value.

Trim the repetitive 'Why X' justification paragraphs (e.g. 'Why xcode-debugging first: 90% of mysterious issues are environment, not code') to a single short rationale, or move them into the linked sub-skills.

Fix the out-of-order section numbering — '### 16. Runtime Console Capture' (line 233) precedes '### 15. Code Signing Issues' (line 248) — to keep navigation predictable.

DimensionReasoningScore

Conciseness

The body is mostly efficient — structured routing tables and trigger lists rather than concept explanations Claude already knows — but the ~120-line 'Example Invocations' section (lines 317-435) largely duplicates the 'Routing Logic' triggers above it, and repeated 'Why X' justification prose could be trimmed, matching the score-2 anchor of mostly efficient but could be tightened.

2 / 3

Actionability

Routing guidance is concrete and copy-paste ready: explicit invoke paths ('skills/xcode-debugging.md'), slash commands ('/axiom:fix-build', '/axiom:console'), and named agents to launch, plus a numbered decision tree mapping symptoms to specific destinations, matching the score-3 anchor for fully executable, specific guidance.

3 / 3

Workflow Clarity

The 'Decision Tree' provides a clear sequenced triage and the routing logic is well-ordered with a 'When NOT to Use' guardrail acting as a conflict-resolution checkpoint; this router involves no destructive/batch operations requiring validate-fix-retry loops, so it meets the score-3 anchor for clear sequencing with explicit checkpoints.

3 / 3

Progressive Disclosure

The SKILL.md serves as an overview router pointing to one-level-deep, clearly signaled references ('Invoke: skills/xcode-debugging.md', 'See axiom-security (skills/code-signing.md)'), with content appropriately split across sibling skills — matching the score-3 anchor for a clear overview with well-signaled one-level-deep references.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it is specific, uses natural trigger terms, answers both what and when with an explicit 'Use when' clause, and scopes itself clearly to environment issues before code debugging. Voice is correctly third person with no first/second-person penalty.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions and symptoms — 'iOS build fails', 'test crashes', 'Xcode misbehaves', 'build failures, compilation errors, dependency conflicts, simulator problems, environment-first diagnostics' — matching the score-3 anchor for enumerating multiple specific actions rather than vague language.

3 / 3

Completeness

It explicitly answers both 'what' ('Covers build failures, compilation errors, dependency conflicts, simulator problems, environment-first diagnostics') and 'when' with an explicit 'Use when ANY iOS build fails, test crashes, Xcode misbehaves, or environment issue occurs before debugging code' trigger clause, matching the score-3 anchor.

3 / 3

Trigger Term Quality

It surfaces natural phrasings a user would actually say ('iOS build fails', 'test crashes', 'Xcode misbehaves', 'build failures', 'simulator problems'), giving good coverage of common variations; 'environment-first diagnostics' is slightly jargon-leaning but the overall natural-keyword coverage matches the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (iOS build/environment issues) with distinct triggers and an explicit scope guard ('before debugging code', 'environment issue occurs before debugging code') that separates it from code-error skills, matching the score-3 anchor of a clear niche unlikely to conflict.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
CharlesWiltgen/Axiom
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.