CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-swift

How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.

Quality

94%

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

The canonical home for this skill is write-swift in emilkowalski/skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 expert-density body that succeeds on actionability and sequencing: nearly every line is a specific rule, API, setting, or ordered recovery path, and the Swift 6.2–6.4 material is exactly what models don't know. The weaknesses are size and shape: a 42KB monolith with zero progressive disclosure into bundle files, plus scattered restatements of basics that could be trimmed.

Suggestions

Split bulk reference material into one-level-deep bundle files (e.g., references/syntax-migration.md for the §15 table, references/performance.md for the §9 levers, references/testing.md for §11), keeping SKILL.md as the defaults table, the concurrency progression, and navigation.

Trim bullets that restate knowledge Claude already has (guard vs if let, access-control level listing, composition-over-inheritance rationale) down to the non-obvious rule they carry, cutting the body's token cost.

Move the toolchain-baseline date ('current release as of August 2026') and version-number detail into a single versioned 'old patterns / toolchain' section so the rest of the body stays evergreen.

DimensionReasoningScore

Conciseness

The bulk is high-signal, novel material (Swift 6.2+ concurrency semantics, InlineArray/Span, SE-0460) that models genuinely don't know, and it is written as terse rules rather than tutorials. A few sections do restate basics Claude already knows ("guard for error conditions", the private/internal/package/public listing, "Composition over inheritance ... monolithic, intrusive"), and the 42KB single file could be tightened — that is more than the level-5 'every token earns its place' but confined enough to stay above level 3's 'some unnecessary explanation'.

4 / 5

Actionability

Guidance is fully concrete throughout: exact build settings ("swiftSettings: [.defaultIsolation(MainActor.self)]"), named APIs with costs ("removeAll(where:) is O(n) total", "InlineArray<N, T>"), tooling commands ("log collect --device --start", "swift task info"), and complete code examples for the common cases (the copy-on-write Material struct, the nonisolated/@concurrent PhotoProcessor, the visualEffect capture-list fix). It never descends to level-4 'minor gaps' territory — specific examples cover the common cases.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with checkpoints and error-recovery loops: the concurrency progression marked "Do not skip steps", the data-race error ladder ("work down this list: don't share it → Sendable value → actor → Mutex"), and the 6-step migration ordered by "The order matters, and mixing steps is how migrations stall" with profiling gates ("only after Instruments shows a hang") and recovery advice. This matches the anchor's feedback loops and clear sequencing.

5 / 5

Progressive Disclosure

There are no bundle files at all — no references/, scripts/, or assets/ — so all ~390 lines live inline in SKILL.md, including content that clearly belongs in separate reference files (the §15 syntax migration table, §9 performance levers, §11 testing details). Section structure itself is good (clear numbered headers, top-level defaults table, quick reference), which rules out level 2's 'no section headers', but 'content that should be separate is inline' fits the level-3 anchor; it cannot score higher without actually splitting content into one-level-deep referenced files.

3 / 5

Total

17

/

20

Passed

Description

100%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 model description: comprehensive concrete capabilities, an explicit and symptom-driven 'Use when' clause, third-person voice, and no filler. It reads as a genuine trigger surface for the domain rather than a summary.

DimensionReasoningScore

Specificity

The description comprehensively enumerates concrete capabilities: "modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros" — every clause names a specific capability, matching the 'comprehensive coverage' anchor. It is dense with signal rather than padded, so it is not the verbose-but-gappy level 4.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is the full capability list up front, and the 'when' is an explicit "Use when ... needs fixing" clause with concrete trigger phrases. This mirrors the level-5 example's structure exactly; level 4 would require the 'when' to be less specific.

5 / 5

Trigger Term Quality

The trigger clause covers natural phrasings users would actually say: "writing, reviewing, or migrating Swift", "a concurrency error, a hang, a data race, a retain cycle, or a performance problem" — concrete symptoms plus synonyms, matching the comprehensive anchor. Nothing relevant to the domain is missing; users asking about Swift concurrency, hangs, or retain cycles would all hit it.

5 / 5

Distinctiveness Conflict Risk

"Modern Swift" with triggers like data races, @concurrent, Swift Testing, and macros is a clear niche — no other plausible skill would trigger on these terms. It is far more specific than the level-4 'minor overlap risk' anchor and matches 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

20

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

.agents/skills/write-swift/SKILL.md

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.