swift-concurrency-expert
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill swift-concurrency-expert90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 a well-structured skill description with explicit 'Use when' triggers and good keyword coverage for Swift developers encountering concurrency issues. The main weakness is that the capabilities could be more concrete—listing specific remediation actions would help Claude understand the full scope of what this skill enables.
Suggestions
Add specific concrete actions like 'add Sendable conformance', 'migrate completion handlers to async/await', 'resolve actor isolation warnings' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Swift Concurrency) and some actions ('review', 'remediation', 'improve', 'fix'), but doesn't list specific concrete actions like 'add Sendable conformance', 'migrate to async/await', or 'resolve data race warnings'. | 2 / 3 |
Completeness | Clearly answers both what ('Swift Concurrency review and remediation for Swift 6.2+') and when ('Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Swift Concurrency', 'concurrency compliance', 'Swift concurrency compiler errors', 'Swift 6.2+', 'review', 'fix'. Good coverage of terms a developer would use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Swift 6.2+ concurrency specifically. The combination of 'Swift Concurrency', version specificity, and 'concurrency compiler errors' creates clear boundaries unlikely to conflict with general Swift or iOS development skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent organization and appropriate progressive disclosure to reference materials. The workflow is clear with proper triage before action. The main weakness is the lack of concrete, executable Swift code examples—the fixes are described conceptually rather than demonstrated with actual code snippets.
Suggestions
Add executable Swift code examples for each common fix pattern (e.g., show before/after code for '@MainActor' annotation, protocol conformance isolation)
Include a concrete example of a compiler diagnostic message paired with its specific fix to make the guidance more actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Swift concurrency concepts. No unnecessary explanations of what actors or Sendable are—just actionable guidance. | 3 / 3 |
Actionability | Provides concrete guidance with specific patterns (e.g., '@MainActor', '@concurrent'), but lacks executable code examples. The fixes are described rather than demonstrated with copy-paste ready Swift code. | 2 / 3 |
Workflow Clarity | Clear two-step workflow with explicit triage checklist before applying fixes. The sequence is logical and the triage step serves as a validation checkpoint before making changes. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview and well-signaled one-level-deep references to detailed materials (swift-6-2-concurrency.md, approachable-concurrency.md, swiftui-concurrency-tour-wwdc.md). | 3 / 3 |
Total | 11 / 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.
- 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.