tessl i github:jeffallan/claude-skills --skill swift-expertUse when building iOS/macOS applications with Swift 5.9+, SwiftUI, or async/await concurrency. Invoke for protocol-oriented programming, SwiftUI state management, actors, server-side Swift.
Validation
75%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
Implementation
42%This skill provides good organizational structure and progressive disclosure through its reference table, but critically lacks actionable code examples. The content reads more like a job description than executable guidance - it tells Claude what to do conceptually but never shows how with concrete implementations.
Suggestions
Add executable Swift code examples for at least 2-3 common patterns (e.g., async/await usage, SwiftUI state management, protocol definition)
Replace abstract constraints like 'Use async/await for asynchronous operations' with concrete before/after code showing the correct pattern
Add validation steps to the workflow, such as specific Xcode build commands or test execution commands
Remove the role definition paragraph - Claude doesn't need to be told it's a 'senior Swift engineer with 10+ years experience'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary verbosity like the role definition paragraph and 'Senior Swift developer with mastery of...' which Claude doesn't need. The constraints lists are reasonable but could be tighter. | 2 / 3 |
Actionability | No executable code examples anywhere. All guidance is abstract ('Use async/await for asynchronous operations', 'Follow Swift API Design Guidelines') without concrete implementations or copy-paste ready snippets. | 1 / 3 |
Workflow Clarity | The 5-step core workflow is listed but lacks validation checkpoints or feedback loops. Steps like 'Optimize - Profile with Instruments' are vague without specific commands or verification criteria. | 2 / 3 |
Progressive Disclosure | Well-structured with clear reference table pointing to specific files for different topics. One-level-deep references are clearly signaled with 'Load When' context for each. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
N/ASomething went wrong
Reviewed
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.