CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-run-tests

Use when the user wants to run XCUITests, parse test results, view test failures, or export test attachments.

70

Quality

85%

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

78%Weight 40%Scale 1-5

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

A highly actionable, well-structured test-runner skill with excellent executable commands and a clear decision tree. Its main weaknesses are repetition that could be tightened and a lack of progressive disclosure — everything lives in one long SKILL.md with no reference files.

Suggestions

Extract the error quick-reference table and 'Common Failure Patterns' catalog into a references/ file (e.g. failures.md) and link to it from SKILL.md to improve progressive disclosure.

Factor the repeated booted-simulator UDID lookup into a single snippet or script (e.g. scripts/booted_udid.sh) and reuse it instead of inlining the command three times.

Add an explicit post-run validation checkpoint (e.g. 'parse the summary; if failed > 0, export attachments and analyze before reporting') to turn the current front-loaded checks into a full validate→fix→retry loop.

DimensionReasoningScore

Conciseness

The body is code-first and lean, assuming Claude's competence without explaining XCUITest fundamentals, but the booted-simulator UDID command is repeated three times and several -scheme/-destination blocks could be DRYed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready xcodebuild and xcresulttool commands with real flags, plus an error quick-reference table and concrete failure diagnoses covering the common cases.

5 / 5

Workflow Clarity

Mandatory first steps and a decision tree give a clear sequenced flow with front-loaded checkpoints, but validation is implicit after test runs rather than a strict validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Section headers organize the ~300-line body well, but all content — including the error quick-reference table and failure-pattern catalog that would suit separate reference files — is inlined with no bundle files or one-level-deep references.

3 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong, concise description that clearly names its niche, lists multiple concrete capabilities, and provides an explicit 'Use when' trigger. Only minor keyword synonym coverage is missing.

DimensionReasoningScore

Specificity

Names the XCUITest domain and lists four concrete actions — 'run XCUITests, parse test results, view test failures, or export test attachments' — matching the comprehensive multi-action anchor.

5 / 5

Completeness

Explicitly states what the skill does (run/parse/view/export) and when to use it via a concrete 'Use when the user wants to...' trigger clause, satisfying both what and when.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('run XCUITests', 'test results', 'test failures', 'test attachments') but misses common synonyms like 'UI tests' and the '.xcresult' extension, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

XCUITest execution and result parsing is a narrow, well-defined niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.