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.
Install with Tessl CLI
npx tessl i github:ravnhq/ai-toolkit --skill swift-concurrency85
Quality
78%
Does it follow best practices?
Impact
97%
1.02xAverage score across 3 eval scenarios
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 follows best practices. It uses third person voice, lists specific Swift concurrency concepts, includes an explicit 'Use when...' clause with multiple trigger scenarios, and uses domain-specific terminology that clearly distinguishes it from other programming skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'async/await, actors, tasks, Sendable conformance' - these are precise technical capabilities within Swift concurrency. | 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' - these are exactly the keywords Swift developers use when seeking help with concurrency. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Swift-specific terminology (actors, Sendable, structured concurrency) that wouldn't overlap with general async programming or other language concurrency skills. | 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 at organization and progressive disclosure, providing a clean overview that points to detailed reference materials. However, it critically lacks actionable content—there are no executable Swift code examples, concrete patterns, or specific implementation guidance in the main skill file itself. The skill reads more like a table of contents than instructional content.
Suggestions
Add at least 2-3 concrete, executable Swift code examples demonstrating core patterns (e.g., basic async/await usage, actor definition, Sendable conformance)
Include a quick-start section with copy-paste ready code for the most common use case (e.g., converting callback-based code to async/await)
Add validation checkpoints to the workflow, such as 'Verify no data race warnings with strict concurrency checking enabled'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. It uses brief section headers with clear pointers to detailed references rather than inline verbosity. | 3 / 3 |
Actionability | The skill lacks concrete, executable code examples. It describes what topics are covered and provides trigger examples, but contains no actual Swift code, commands, or copy-paste ready guidance for implementing concurrency patterns. | 1 / 3 |
Workflow Clarity | The workflow section provides a 3-step sequence but lacks validation checkpoints or feedback loops. For a skill covering complex concurrency patterns with potential data races, explicit validation steps would be expected. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview pointing to one-level-deep references (rules/_sections.md, references/swift-concurrency.md). Content is well-organized with clear navigation signals and appropriate separation of concerns. | 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 | |
- 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.