Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 exemplary skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that users would naturally use, explicit 'Use when' guidance with enumerated scenarios, and a clearly defined niche in Swift concurrency that distinguishes it from other programming skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Diagnose data races', 'convert callback-based code to async/await', 'implement actor isolation patterns', 'resolve Sendable conformance issues', and 'guide Swift 6 migration'. | 3 / 3 |
Completeness | Clearly answers both what (diagnose, convert, implement, resolve, guide) AND when with an explicit 'Use when developers mention:' clause followed by 8 specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including 'Swift Concurrency', 'async/await', 'actors', 'tasks', 'Swift 6', 'data races', 'thread safety', '@MainActor', 'Sendable', and even specific linter warning types. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Swift concurrency specifically; the combination of Swift-specific terms like 'actor isolation', 'Sendable', '@MainActor', and 'Swift 6 migration' makes it unlikely to conflict with general async programming or other language skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while providing highly actionable guidance. The diagnostic table with specific compiler messages mapped to fixes is particularly valuable, and the migration validation loop provides clear workflow with explicit checkpoints. The progressive disclosure through the Reference Router is well-organized and easy to navigate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Swift. It uses tables for quick reference, avoids explaining basic concepts, and every section serves a clear purpose without padding. | 3 / 3 |
Actionability | Provides concrete, executable code examples (network request with UI update, parallel processing), specific diagnostic-to-fix mappings, and copy-paste ready patterns. The Common Diagnostics table gives exact fixes for specific compiler messages. | 3 / 3 |
Workflow Clarity | The Migration Validation Loop provides explicit numbered steps with validation checkpoints (Build → Fix → Rebuild → Test → proceed). The Verification Checklist reinforces this with clear sequencing and the instruction to 'never batch unrelated fixes.' | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear Reference Router section pointing to one-level-deep reference files organized by topic. The main skill provides quick fixes and overview, with detailed content appropriately delegated to specific reference files. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
05d62d7
Table of Contents
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.