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

63%

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

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

The skill is a well-sequenced, highly actionable auditing workflow with strong validation checkpoints and minimal padding. Its main weakness is progressive disclosure: all detail is inlined and the cross-skill links point to skills not present in this bundle.

Suggestions

Move the eight pattern definitions and the compound-finding table into a separate references file, leaving SKILL.md as an overview that signals where the detail lives.

Provide executable Swift fix snippets (not just 'Add @MainActor') for at least the CRITICAL/HIGH patterns so fixes are copy-paste ready.

Clarify whether the referenced skills (axiom-concurrency, axiom-performance, axiom-tools) are real bundle files or external pointers, and link them one level deep with clear navigation.

DimensionReasoningScore

Conciseness

The body is dense and operational — pattern tables, grep strings, and severity rules with little conceptual padding — though a few sections (false positives, compound tables) could be trimmed slightly.

4 / 5

Actionability

It gives concrete grep patterns, file exclusions, severity tiers, fix recipes, and a ready-to-emit output template, but some fixes are one-line directives rather than executable Swift examples.

4 / 5

Workflow Clarity

Five sequenced phases with explicit verification steps (Read context before reporting, compiler-diagnostics precedence, output-before-proceeding checkpoint) and a feedback-oriented output format that ties findings back to each phase.

5 / 5

Progressive Disclosure

Structure is clear within SKILL.md but there are no bundle files despite references to other skills (axiom-concurrency, axiom-performance, axiom-tools), and the ~250-line body inlines pattern detail that could live in separate reference files.

3 / 5

Total

16

/

20

Passed

Description

51%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 is a pure trigger clause with strong 'when' guidance but no 'what' statement, leaving the skill's actual capabilities unstated. Trigger terms are good and the niche is distinct.

Suggestions

Add a concrete 'what' clause before the trigger, e.g. 'Detects Swift 6 concurrency anti-patterns and missing isolation patterns. Use when...'

Include synonyms users naturally say such as 'race conditions', 'thread safety', and 'Sendable' alongside the current trigger terms.

Replace the implicit second-person framing by stating actions in third person (e.g. 'Audits Swift code for...') to strengthen the specificity of capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('concurrency checking, Swift 6 compliance, data race prevention, async code review') but provides no concrete actions — it only says 'Use when' with trigger topics rather than what the skill actually does (audit, detect, report).

2 / 5

Completeness

It has an explicit 'Use when...' clause giving clear trigger guidance, but the 'what' is entirely absent — there is no statement of what the skill does, only when to invoke it, so the what/when pair is incomplete.

3 / 5

Trigger Term Quality

It surfaces several natural phrases a user would say ('concurrency checking', 'async code review', 'data races') though it leans technical and omits common synonyms like 'thread safety' or 'race conditions'.

4 / 5

Distinctiveness Conflict Risk

The Swift 6 concurrency niche is fairly specific and unlikely to trigger for unrelated skills, though 'async code review' could overlap with general code-review skills.

4 / 5

Total

13

/

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.