CtrlK
BlogDocsLog inGet started
Tessl Logo

guide-swift-concurrency

Swift concurrency patterns — actors, structured concurrency, cancellation, async streams, GCD migration, strict-concurrency diagnostics, common bug patterns. Use when writing, reviewing, or debugging concurrent Swift code.

72

Quality

89%

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

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 well-structured guide skill that is lean, clearly sequenced, and uses one-level-deep references effectively. Actionability and workflow clarity are strong but could be nudged higher by surfacing a small amount of executable detail or an explicit verification checkpoint inline.

Suggestions

Add one short inline code example or a concrete grep pattern in Core Instructions (e.g., a sample regex for hotspot scanning) to lift actionability from guidance-heavy to copy-paste-ready.

Include an explicit validation/verification checkpoint in the Review Process (e.g., 'After fixes, re-run the relevant checks from steps 1–11 to confirm resolution') to add a feedback loop.

Consider noting the Swift version dependency (6.2) in the References table row for new-features.md so version-sensitive guidance is discoverable at a glance.

DimensionReasoningScore

Conciseness

Lean and efficient — terse directives like 'Prefer structured concurrency (task groups) over unstructured (Task {})' and 'Do not suggest @unchecked Sendable' assume Claude's competence with no padding or concept re-explanation.

5 / 5

Actionability

Core Instructions give concrete dos/don'ts and the 12-step review process maps each check to a specific reference file, but the body itself defers all executable detail to references rather than providing copy-paste-ready guidance.

4 / 5

Workflow Clarity

A clear numbered 12-step review sequence with conditional branches ('If strict-concurrency errors exist…', 'If reviewing tests…'), but no explicit validate→fix→retry feedback loop; this is a read-only review skill so the destructive-cap rule does not bind.

4 / 5

Progressive Disclosure

A concise overview with a 12-step process and a well-organized References table; each of the 12 referenced files exists and is one level deep with clear topic-to-file signaling, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific description that clearly scopes a Swift-concurrency niche and provides an explicit 'Use when' trigger. Trigger-term coverage is broad but could add common synonyms like async/await.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — 'actors, structured concurrency, cancellation, async streams, GCD migration, strict-concurrency diagnostics, common bug patterns' — giving comprehensive domain coverage with no significant gaps.

5 / 5

Completeness

Explicitly answers both 'what' (enumerated concurrency patterns) and 'when' ('Use when writing, reviewing, or debugging concurrent Swift code') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger phrasing ('Use when writing, reviewing, or debugging concurrent Swift code') with good keywords (actors, async streams, GCD), but missing common synonyms like 'async/await', 'Task groups', or '.swift'.

4 / 5

Distinctiveness Conflict Risk

Niche is sharply defined — Swift concurrency specifically — with distinct triggers (concurrent Swift code, actors, GCD migration) and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Prisma-Labs-Dev/apple-skills
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.