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.

68

Quality

82%

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

65%

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

The body delivers highly executable command guidance and a clear test-running workflow, but it is a monolithic single file with some redundancy and lacks explicit validation feedback loops for its batch/export operations. Splitting reference material into bundle files and tightening repeated blocks would raise its score.

Suggestions

Move the Error Quick Reference, Integration with Other Agents, and Resources sections into a references/ file and link to it from the body to improve progressive disclosure.

Add an explicit validate->fix->retry feedback loop for test runs (e.g., re-run only failing tests after a fix) rather than only delegating failures to other agents.

De-duplicate the simulator-UDID discovery snippet by defining it once and reusing it, tightening the conciseness of the Running Tests section.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence (no basic concept explanations), but the simulator-UDID discovery block repeats and the Output Format/Decision Tree/Error tables pad length; not a 3 because several sections could be tightened, not a 1 because there is no padded conceptual filler.

2 / 3

Actionability

Provides copy-paste-ready xcodebuild and xcresulttool commands with concrete flags and output parsing (e.g., '-only-testing', '--only-failures'); not a 2 because the code is executable rather than pseudocode.

3 / 3

Workflow Clarity

Sequence is clear with mandatory first steps and a decision tree, but the test-run/export operations lack an explicit validate->fix->retry feedback loop (failure handling is delegated out); per rubric notes, missing validation in batch/risky ops caps this at 2, and not a 1 because steps are clearly sequenced.

2 / 3

Progressive Disclosure

No bundle files exist and everything is inlined in one ~310-line SKILL.md with sections (error reference, integration, resources) that could be split out; not a 1 because sections are labeled and organized, not a 3 because there is no one-level-deep reference structure or signaled navigation.

2 / 3

Total

9

/

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 concise, action-oriented, and includes an explicit 'Use when...' trigger covering both what the skill does and when to invoke it. It is specific to XCUITest workflows and unlikely to conflict with unrelated skills.

DimensionReasoningScore

Specificity

Lists four concrete actions ('run XCUITests, parse test results, view test failures, or export test attachments'), matching the multi-action anchor; not a 2 because the actions are specific rather than a single named domain.

3 / 3

Completeness

Explicitly answers what (run/parse/view/export) and when via an explicit 'Use when the user wants to...' clause; not a 2 because the trigger is stated, not merely implied.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('run XCUITests', 'test results', 'test failures', 'export test attachments') with good coverage; not a 2 because common variations are present rather than missing.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (XCUITest running and result parsing) with distinct triggers unlikely to collide with other skills; not a 2 because it is narrowly scoped rather than broadly overlapping.

3 / 3

Total

12

/

12

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.