CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-concurrency

Use when the user mentions concurrency checking, Swift 6 compliance, data race prevention, or async code review.

56

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./axiom-codex/skills/axiom-audit-concurrency/SKILL.md
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.

This is a well-structured, actionable auditor skill with a clear phased workflow and explicit validation checkpoints. The main gap is the absence of progressive-disclosure bundle files to offload detailed pattern references and code-fix examples.

DimensionReasoningScore

Conciseness

The body is dense and efficient — grep patterns, tables, and terse pattern descriptions — without explaining concepts Claude already knows, though a few repeated Notes and caveats could be trimmed.

4 / 5

Actionability

It provides concrete grep search strings, context-verification steps, and per-pattern fix prescriptions, but fixes are described in prose rather than as copy-paste Swift code examples, leaving minor gaps.

4 / 5

Workflow Clarity

The five phases are explicitly sequenced with validation checkpoints — "use Read to verify the surrounding context before reporting", "Require evidence from the Phase 1 map — don't speculate" — and the output format provides a clear feedback structure.

5 / 5

Progressive Disclosure

Content is well-organized into phases with one-level-deep cross-references to related skills, but all detail lives in a single SKILL.md with no bundle files, so some pattern/fix detail that could be split out is inlined.

4 / 5

Total

17

/

20

Passed

Description

47%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.

The description has a strong, explicit trigger clause with good keyword coverage, but it completely omits what the skill does, leaving it unbalanced. Adding a concrete statement of the skill's actions would substantially raise specificity and completeness.

Suggestions

Lead with a concrete "what" clause before the trigger, e.g. "Detects Swift 6 concurrency issues including data races, missing @MainActor isolation, and unsafe task capture. Use when the user mentions concurrency checking, Swift 6 compliance, data race prevention, or async code review."

Add a few natural synonyms to broaden trigger coverage, such as "thread safety" and "actor isolation".

Avoid relying on the skill name alone to convey the capability; the description should stand alone.

DimensionReasoningScore

Specificity

The description only states trigger conditions ("Use when the user mentions concurrency checking, Swift 6 compliance, data race prevention, or async code review") and names the domain but lists no concrete actions, matching the anchor that names the domain with minimal/generic actions.

2 / 5

Completeness

It provides an explicit "Use when..." clause (the "when") but omits any statement of what the skill does, matching the anchor where only the "when" is present without a "what".

2 / 5

Trigger Term Quality

It includes natural user-facing terms ("concurrency checking", "Swift 6 compliance", "data race prevention", "async code review") with good coverage, though common synonyms like "thread safety" or "actors" are missing, fitting just above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The Swift 6 concurrency niche and specific trigger phrases make it mostly distinct from other skills, with only minor overlap risk against closely related code-review skills.

4 / 5

Total

12

/

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.