swift-concurrency-expert

Swift concurrency review/fix: compiler errors, Sendable, isolation, remediation.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/swift-concurrency-expert/SKILL.md

Quality

Content

86%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 lean, well-structured skill body that respects token budget, gives concrete fix recipes keyed to situation categories, and cleanly pushes detail into two real one-level-deep reference files. The only gap is the absence of an explicit post-fix verification step and illustrative before/after examples.

Dimension	Reasoning	Score
Conciseness	The body is ~30 lean lines with no padding or explanation of concepts Claude already knows ("Prefer edits that preserve existing behavior while satisfying data-race safety"); every token earns its place, with only the attribution line being arguably extraneous.	5 / 5
Actionability	Concrete Swift syntax is given for each fix category ("annotate the type or relevant members with `@MainActor`", "`extension Foo: @MainActor SomeProtocol`", "move expensive work into a `@concurrent` async function"), so the guidance is executable as instruction-only material. It falls short of 5 because no before/after code examples illustrate the common cases.	4 / 5
Workflow Clarity	The triage → smallest-safe-fix sequence is clearly ordered with specific sub-steps ("Capture the exact compiler diagnostics", "Identify the current actor context"), and the simple-skill exception applies. Not 5 because there is no explicit post-fix verification step (e.g., re-compile to confirm the diagnostic is resolved); not 3 because the sequence and decision mapping are well defined.	4 / 5
Progressive Disclosure	The SKILL.md is a lean overview with well-signaled, one-level-deep references ("See `references/swift-6-2-concurrency.md` for Swift 6.2 changes, patterns, and examples"); both referenced files exist and contain no nested references, so content is appropriately split and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

62%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 terse, domain-specific description that clearly communicates what the skill does and is highly distinguishable from other skills. Its main weakness is the complete absence of an explicit "when to use" trigger clause and the omission of common natural trigger terms users would say.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user hits Swift concurrency compiler errors, data-race safety warnings, or mentions Sendable, actor isolation, @MainActor, async/await, or migrating to Swift 6."

Include the natural synonyms users actually say — "data race", "actor", "@MainActor", "async/await", "Swift 6" — alongside the existing terms to broaden trigger coverage.

State the concrete actions as verbs ("Reviews and fixes Swift concurrency compiler errors, Sendable violations, and actor-isolation problems") rather than a bare keyword list, to sharpen the what-it-does statement.

Dimension	Reasoning	Score
Specificity	The description lists several specific concrete items — "compiler errors, Sendable, isolation, remediation" — beyond just naming the Swift concurrency domain. It is not 5 because the coverage reads as a keyword list rather than comprehensive concrete actions, and not 3 because it clearly exceeds 1-2 actions.	4 / 5
Completeness	The "what" is clear (review/fix Swift concurrency issues via Sendable, isolation, remediation of compiler errors), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	Terms like "Swift concurrency", "Sendable", and "compiler errors" are ones users would naturally say, but common variations and synonyms are missing — "data race", "actor"/"@MainActor", "async/await", "Swift 6". Not 4 because several natural trigger phrases users would actually use are absent.	3 / 5
Distinctiveness Conflict Risk	"Swift concurrency" combined with domain-distinct terms (Sendable, isolation) carves a clear niche with minimal conflict risk; it would not naturally trigger for unrelated skills. Only trivial overlap exists with a hypothetical generic Swift code-review skill, which does not rise to the level of anchor 4's "minor overlap risk with closely related skills".	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: steipete/agent-scripts
Path: skills/swift-concurrency-expert/SKILL.md
Commit: 3f8c6a3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.