developing-ios-apps
Develops iOS/macOS applications with XcodeGen, SwiftUI, and SPM. Handles Apple Developer signing, notarization, and CI/CD pipelines. Triggers on XcodeGen project.yml, SPM dependency issues, device deployment, code signing errors (Error -25294, keychain mismatch, adhoc fallback, EMFILE, notarization credential conflict, continueOnError), camera/AVFoundation debugging, iOS version compatibility, "Library not loaded @rpath", Electron @electron/osx-sign/@electron/notarize config, notarytool, GitHub Actions secrets in conditionals, or certificate/provisioning problems. Use when building iOS/macOS apps, fixing Xcode build failures, deploying to real devices, or configuring CI/CD signing pipelines.
94
92%
Does it follow best practices?
Impact
96%
1.23xAverage score across 3 eval scenarios
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 excellent skill description that thoroughly covers specific capabilities, includes rich trigger terms spanning error codes, tool names, and common user phrases, and explicitly states both what the skill does and when to use it. The description is dense with actionable detail without being padded with fluff, making it highly effective for skill selection among many candidates.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: developing iOS/macOS apps with XcodeGen/SwiftUI/SPM, handling Apple Developer signing, notarization, CI/CD pipelines, camera/AVFoundation debugging, and Electron signing config. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (develops iOS/macOS apps, handles signing/notarization/CI/CD) and 'when' with an explicit 'Use when...' clause covering building apps, fixing build failures, deploying to devices, and configuring CI/CD signing pipelines. Also has a 'Triggers on' section listing specific scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually encounter: specific error codes (Error -25294), common error messages ('Library not loaded @rpath'), tool names (XcodeGen, notarytool, @electron/osx-sign), file names (project.yml), and natural phrases like 'code signing errors', 'device deployment', 'Xcode build failures'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in Apple platform development, XcodeGen, code signing, and notarization. The specific error codes, tool names, and Apple-ecosystem terminology make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 high-quality skill file that covers a complex domain (iOS/macOS development, signing, CI/CD) with strong actionability and excellent structure. The critical warnings table at the top is an effective pattern for surfacing common pitfalls. Minor verbosity in explanatory sections (e.g., SPM dynamic framework background) could be trimmed, but overall the content is well-organized and immediately useful.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code blocks, but includes some explanatory content that Claude wouldn't need (e.g., explaining what dynamic vs static frameworks are, explaining why SPM embedding fails). The 'Why This Happens' section under SPM could be trimmed. However, most content earns its place. | 2 / 3 |
Actionability | Excellent actionability throughout — executable code snippets, specific bash commands, concrete YAML configurations, and copy-paste ready examples. The code signing checklist, camera debugging patterns, and XcodeGen configurations are all directly usable. Even error messages are quoted verbatim for easy matching. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The code signing section has a 5-step checklist with critical details at each step, a three-layer fail-fast defense, and verification commands. Device deployment has numbered first-time setup steps. The camera debugging checklist provides a clear diagnostic sequence. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the main file provides actionable overviews and quick references, then clearly links to 5 separate reference files for detailed content (xcodegen-full.md, swiftui-compatibility.md, camera-avfoundation.md, testing-mainactor.md, apple-codesign-notarize.md). References are one level deep and well-signaled with descriptive labels. | 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.
- Repository
- daymade/claude-code-skills
- Commit
80e94fd
- 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.