CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-concurrency

Use when writing ANY async code, actors, threads, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.

68

Quality

83%

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

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

An effective router skill that excels at progressive disclosure, pointing cleanly to one-level-deep reference files with multiple navigation aids. Its main weakness is redundant routing across the Quick Reference, Decision Tree, and Example Invocations sections, which inflates token cost without adding guidance.

Suggestions

Collapse the 'Example Invocations' section into the Quick Reference table or Decision Tree — it duplicates the same file-routing mappings already shown above it.

Merge 'Critical Patterns' bullets into the Quick Reference rows or trim them to only the entries that add routing signal not already covered by the table.

Add one or two inline copy-paste snippets (e.g., a minimal actor/Sendable example) so the skill is actionable without always requiring a file read for the most common cases.

DimensionReasoningScore

Conciseness

Each section is lean and assumes Claude's intelligence (no basic concept explanations), but the Quick Reference table, Decision Tree, Critical Patterns, and Example Invocations sections redundantly route to the same files, which is trimmable padding; not a 3 because no section is itself verbose.

4 / 5

Actionability

Provides concrete file paths and explicit routing rules ("data race errors, Sendable conformance → skills/swift-concurrency.md") that are directly executable; not a 5 because it contains no inline code or commands and relies entirely on external files.

4 / 5

Workflow Clarity

A clear sequenced routing workflow via the decision tree and numbered list, plus explicit conflict-resolution guidance between overlapping skills; not a 5 because there are no validation checkpoints, though they are largely unnecessary for a non-destructive routing skill.

4 / 5

Progressive Disclosure

This is a textbook progressive-disclosure hub: a concise overview with well-signaled, one-level-deep references (skills/*.md) organized via a Quick Reference table and decision tree, with content appropriately split into separate files and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

87%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, well-scoped description that explicitly covers both capability and trigger conditions with Swift-specific terminology. It is highly specific and distinctive, with only minor room for additional natural-language synonyms.

DimensionReasoningScore

Specificity

Lists several specific concrete items ("Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns") rather than vague language, with only minor coverage gaps; not a 5 because the framing is topic-list rather than a comprehensive set of distinct concrete actions.

4 / 5

Completeness

Explicitly answers both what ("Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns") and when ("Use when writing ANY async code... or seeing ANY concurrency error") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say ("async code", "actors", "threads", "concurrency error", "data races", "Swift 6"), but a few common variants/synonyms are missing, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Carves a clear Swift concurrency niche with distinct, framework-specific triggers (@MainActor, Sendable, Swift 6) and minimal overlap risk with unrelated skills.

5 / 5

Total

18

/

20

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.