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 that users would naturally use when encountering these issues, and clearly delineates both what the skill does and when it should be activated. The description is dense with actionable detail without being padded with fluff, and its Apple-ecosystem focus makes it highly distinctive.
| 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 Xcode build failures, deploying to devices, and configuring CI/CD signing pipelines. Also includes a 'Triggers on' section with 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', 'keychain mismatch'. These are terms users would naturally use when seeking help. | 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 strong, well-structured skill that covers a broad domain (iOS/macOS development, signing, CI/CD) with highly actionable content. Its greatest strengths are the concrete error-to-solution mappings, executable code examples, and excellent progressive disclosure to reference files. The main weakness is some verbosity in explanatory sections (particularly the SPM dynamic framework explanation) that could be tightened without losing clarity.
Suggestions
Trim the 'Why This Happens' explanation in the SPM Dynamic Framework section — Claude understands static vs dynamic linking; a single sentence noting XcodeGen's limitation would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but some sections include explanations Claude would already know (e.g., 'Why This Happens' explaining static vs dynamic frameworks, explaining what notarization does). The SPM dynamic framework section is particularly verbose with its root cause explanation. However, most content earns its place. | 2 / 3 |
Actionability | Highly actionable throughout — executable code snippets, specific bash commands, concrete YAML configurations, exact error messages with fixes, and copy-paste ready examples. The code signing checklist, XcodeGen config, and camera debugging patterns are all immediately usable. | 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 with verification commands, and the device deployment section has clear first-time setup steps. The SPM fix includes a clear sequence with verification. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in SKILL.md and clear references to detailed files (camera-avfoundation.md, apple-codesign-notarize.md, xcodegen-full.md, etc.). References are one level deep, well-signaled with descriptive labels, and the main file contains enough to act on common cases while pointing to deeper resources for advanced needs. | 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
bbf87f3
- 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.