CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-testing

Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.

72

Quality

88%

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

77%

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

A well-structured router with concrete navigation and clear routing logic, weakened by redundant repetition across four sections and by references to skill files that are absent from the bundle.

Suggestions

Collapse the Quick Reference table, Decision Tree, numbered list, and Critical Patterns into a single routing section to remove the four-way repetition of the same destinations.

Resolve or remove the dangling skills/*.md references (e.g. skills/swift-testing.md, skills/ui-testing.md) — none of these files exist in the bundle, so progressive-disclosure navigation currently leads nowhere.

If the referenced files live in a sibling skills/ directory outside this bundle, note that explicitly so the references are verifiable rather than appearing broken.

DimensionReasoningScore

Conciseness

The same routing is repeated four ways — Quick Reference table, Decision Tree, numbered list, and Critical Patterns — so the body could be tightened; it does not waste tokens explaining concepts Claude already knows, but the redundancy is unnecessary.

2 / 3

Actionability

Concrete, copy-paste-ready navigation: specific file paths ("skills/swift-testing.md"), named agents ("testing-auditor"), and exact commands ("/axiom:audit testing"); for an instruction-only router this guidance is actionable.

3 / 3

Workflow Clarity

Routing is clearly sequenced via the Decision Tree and numbered list, and the Example Invocations show multi-step checks (e.g. "Check codebase: XCUIApplication/XCUIElement? → skills/ui-testing.md").

3 / 3

Progressive Disclosure

The overview-router pattern with one-level-deep "See skills/X.md" references is well signaled, but the referenced skills/*.md files are not present in the bundle, so the navigation targets are broken/unverified.

2 / 3

Total

10

/

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.

A strong, third-person description with an explicit "Use when" trigger, concrete actions, and natural trigger terms. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "writing ANY test", "debugging flaky tests", "making tests faster", "choosing Swift Testing vs XCTest" — rather than vague language.

3 / 3

Completeness

Explicitly answers both: what ("Covers unit tests, UI tests, async testing, test architecture") and when ("Use when writing ANY test, debugging flaky tests, making tests faster...").

3 / 3

Trigger Term Quality

Covers natural terms users say ("writing test", "flaky tests", "make tests faster", "unit tests", "UI tests", "async testing", "Swift Testing vs XCTest") with good variation.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to Swift Testing vs XCTest and iOS test types, with distinctive triggers unlikely to fire for unrelated skills.

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.