CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-testing

Use when the user wants to audit test quality, find flaky test patterns, speed up test execution, or prepare for Swift Testing migration.

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 highly actionable, well-sequenced auditor prompt with concrete detection patterns, fix examples, and verification steps. Its main weakness is conciseness and progressive disclosure: it is a long single-file wall of text with some explanatory padding that could be trimmed or offloaded to reference files.

Suggestions

Trim explanatory 'Issue/Why it matters' prose and the OS27 rationale to one line each; Claude already understands flaky-test and concurrency trade-offs, so lead with the grep pattern and fix.

Extract the per-category grep patterns and fix code into a reference file (e.g. references/anti-patterns.md) and keep SKILL.md as a phased overview with one-level-deep links, improving progressive disclosure and token budget.

Consolidate the Phase 3/4 question and compound-finding tables into a single reference table to reduce repetition between the two phases.

DimensionReasoningScore

Conciseness

Mostly efficient and actionable, but at ~340 lines it carries explanatory prose Claude doesn't need (e.g. 'Issue: Arbitrary waits cause timing-dependent failures, especially in CI' and the long OS27 rationale paragraph) that could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete grep regexes, exact file globs, executable Swift fix examples, and precise detection/flagging criteria — copy-paste ready guidance throughout, matching the top anchor.

3 / 3

Workflow Clarity

Sequenced across Phase 1–5 with explicit verification ('read surrounding context to verify it's a real issue before reporting'), cross-reference tables, a false-positive checklist, and a defined output format — clear sequence with validation checkpoints for a batch audit.

3 / 3

Progressive Disclosure

Sections are well-organized, but no bundle files exist and the entire auditor lives inline in one ~340-line SKILL.md; external skill references (axiom-testing, axiom-ai, test-failure-analyzer) are signaled but inline content that could be split keeps it below the top anchor.

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 description: third-person voice, explicit 'Use when' trigger, and four concrete auditing actions that double as natural trigger terms. It clearly answers both what the skill does and when to invoke it with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'audit test quality, find flaky test patterns, speed up test execution, or prepare for Swift Testing migration' — matching the anchor for naming several specific actions rather than vague language.

3 / 3

Completeness

The 'what' (the four auditing actions) and the 'when' (explicit 'Use when the user wants to...' trigger) are both present and explicit, satisfying the top completeness anchor.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('test quality', 'flaky test patterns', 'speed up test execution', 'Swift Testing migration'); not jargon-only and covers the common phrasings a developer would use.

3 / 3

Distinctiveness Conflict Risk

The Swift/iOS testing-audit niche with triggers like 'flaky test patterns' and 'Swift Testing migration' is distinct and unlikely to fire for unrelated skills.

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.