jbvc/ios-developer
Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.
57
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 solid skill description with strong trigger terms and clear 'when to use' guidance. Its main weakness is that the capabilities are listed more as technology buzzwords ('Masters iOS 18, SwiftUI, UIKit integration') rather than concrete actions the skill performs. The use of 'Masters' as a verb feels like a claim/buzzword rather than a specific capability description.
Suggestions
Replace 'Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking' with concrete actions like 'Builds SwiftUI views, integrates UIKit components, implements Core Data persistence, handles networking and API calls'.
Avoid the word 'Masters' which is a vague claim; instead describe what the skill actually does with those technologies.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (iOS development) and mentions several technologies (Swift/SwiftUI, UIKit, Core Data, networking, App Store optimization), but these read more like a technology list than concrete actions. 'Develop native iOS applications' is the only action verb, and 'Masters' is not an action description. | 2 / 3 |
Completeness | Answers both 'what' (develop native iOS applications with Swift/SwiftUI, UIKit integration, Core Data, networking, App Store optimization) and 'when' ('Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'iOS', 'Swift', 'SwiftUI', 'UIKit', 'Core Data', 'App Store', 'native iOS development' are all terms users would naturally use when requesting iOS development help. Covers multiple variations and specific frameworks. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to native iOS development with specific platform markers (iOS 18, SwiftUI, UIKit, App Store). Unlikely to conflict with general mobile development, Android, or web development skills due to the iOS-specific terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a capability catalog or persona description rather than an actionable skill file. It lists dozens of iOS technologies and concepts Claude already knows without providing any concrete code, specific workflows, or novel project-specific guidance. The content would need a complete rewrite to be useful—replacing the enumeration of known capabilities with executable examples, specific architectural patterns with code, and clear step-by-step workflows with validation checkpoints.
Suggestions
Replace the extensive 'Capabilities' bullet lists with 2-3 concrete, executable Swift/SwiftUI code examples demonstrating key patterns (e.g., a SwiftUI view with Core Data, async/await networking, or proper error handling).
Add a clear multi-step workflow for common iOS development tasks (e.g., setting up a new project, implementing a feature end-to-end) with explicit validation checkpoints like build verification and testing steps.
Move detailed reference material (architecture patterns, testing strategies, App Store guidelines) into the referenced 'resources/implementation-playbook.md' and keep SKILL.md as a concise overview with actionable quick-start guidance.
Remove all sections that merely list technologies Claude already knows (Security, Networking, Performance, etc.) and replace them with project-specific conventions, preferred patterns, or constraints unique to this skill's context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with information Claude already knows. The bulk of the content is a massive enumeration of iOS capabilities, frameworks, and concepts (Core Data, URLSession, ARKit, etc.) that Claude is already well-versed in. The 'Capabilities' section alone lists dozens of technologies without adding any novel, project-specific guidance. This is essentially a resume, not a skill. | 1 / 3 |
Actionability | Contains zero executable code, no concrete commands, no specific examples, and no copy-paste ready snippets. Everything is described at an abstract level ('URLSession with async/await for modern networking', 'Core Data with SwiftUI integration'). The 'Response Approach' section is a generic numbered list of vague directives rather than actionable instructions. | 1 / 3 |
Workflow Clarity | No clear multi-step workflow is defined. The 'Response Approach' lists 8 high-level steps but they are abstract principles, not a concrete workflow with validation checkpoints. There are no feedback loops, no verification steps, and no sequenced process for any iOS development task. | 1 / 3 |
Progressive Disclosure | There is a single reference to 'resources/implementation-playbook.md' for detailed examples, which is a good signal of progressive disclosure. However, the main file itself is a monolithic wall of bullet-pointed lists that could be dramatically condensed or split into separate reference files. The structure exists but the content organization is poor. | 2 / 3 |
Total | 5 / 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_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents