swift-concurrency
Swift Concurrency patterns — async/await, actors, tasks, Sendable conformance. Use when writing async/await code, implementing actors, working with structured concurrency, or ensuring data race safety.
85
78%
Does it follow best practices?
Impact
97%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/swift-concurrency/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific Swift concurrency capabilities, includes natural trigger terms that developers would use, explicitly states both what it does and when to use it, and is distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'async/await, actors, tasks, Sendable conformance' - these are precise technical capabilities, not vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Swift Concurrency patterns — async/await, actors, tasks, Sendable conformance') AND when ('Use when writing async/await code, implementing actors, working with structured concurrency, or ensuring data race safety'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'async/await', 'actors', 'structured concurrency', 'data race safety', 'Sendable' - these match how Swift developers naturally discuss concurrency. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Swift-specific concurrency terminology that wouldn't overlap with general async patterns in other languages or other Swift skills; 'Sendable conformance' and 'actors' are uniquely Swift concurrency concepts. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels as a navigation document with excellent progressive disclosure and token efficiency, but fails to provide actionable guidance. It describes where to find information rather than providing concrete, executable Swift Concurrency patterns. The troubleshooting section is generic boilerplate that could apply to any skill.
Suggestions
Add at least 2-3 executable Swift code examples demonstrating core patterns (e.g., async/await conversion, actor implementation, Sendable conformance)
Replace the generic troubleshooting section with Swift Concurrency-specific issues (e.g., 'Actor reentrancy causing unexpected state', 'Sendable conformance errors with closures')
Make the workflow actionable with specific steps like 'Check for @MainActor requirements' or 'Verify Sendable conformance at boundaries'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, serving as a navigation hub without explaining Swift concepts Claude already knows. Every section points to detailed resources without redundant explanation. | 3 / 3 |
Actionability | The skill contains no executable code, no concrete commands, and no specific examples of Swift Concurrency patterns. It only describes what exists elsewhere and provides abstract workflow steps like 'Apply the skill rules' without showing how. | 1 / 3 |
Workflow Clarity | The 3-step workflow is present but vague ('Apply the skill rules', 'Validate output quality'). No concrete validation checkpoints or specific actions are defined for multi-step concurrency refactoring tasks. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to rules/_sections.md and references/swift-concurrency.md. Content is well-organized with clear navigation signals for each topic area. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- ravnhq/ai-toolkit
- Commit
7b466be
- 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.