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.

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

81%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-sequenced auditor prompt with strong validation guardrails. The main weakness is token-efficiency: redundant grep listings and an over-long OS27 section could be trimmed or externalized.

Suggestions

Deduplicate the grep patterns: list each regex once, either in the by-category block or the per-category sections, not both.

Tighten the OS27 (1.4) AI-evaluation-gate section — its three-bullet rationale can be condensed without losing the pin/measure/guardrail guidance.

Consider moving the Phase 5 scoring table and output-format template into a referenced reference file to reduce body length.

DimensionReasoningScore

Conciseness

Mostly efficient but padded in places: grep patterns are listed twice (once grouped by category, again within each category) and the OS27 AI-eval gate section is verbose relative to its weight.

3 / 5

Actionability

Provides concrete grep regexes, copy-paste-ready Swift fix examples, and explicit detection/fix pairs covering common cases.

5 / 5

Workflow Clarity

Clear five-phase sequence with a verification checkpoint ('read surrounding context to verify it's a real issue before reporting'), an explicit false-positive list, and output-limit guardrails.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clearly labeled sections and no nested references, though the file is long and some material (e.g. grep pattern tables) could be split out.

4 / 5

Total

17

/

20

Passed

Description

83%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, trigger-rich description that names several concrete actions and an explicit 'Use when' clause. Minor gains available from adding synonyms and file-extension terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'audit test quality, find flaky test patterns, speed up test execution, or prepare for Swift Testing migration' — giving comprehensive coverage of the skill's purpose.

5 / 5

Completeness

Explicitly answers 'when' via the 'Use when the user wants to...' clause with concrete triggers, and the 'what' is conveyed through the action list, though the capability is stated through triggers rather than as a standalone action statement.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('flaky test patterns', 'speed up test execution', 'Swift Testing migration') but is missing some synonyms and file-extension variants.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Swift Testing migration, flaky-test detection) with triggers unlikely to fire for unrelated skills.

5 / 5

Total

18

/

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.