xcode-project-analyzer
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.
89
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 a strong skill description that clearly defines its scope (Xcode project build configuration auditing), lists concrete actions, and provides an explicit 'Use when...' clause with rich, natural trigger terms. It is highly distinctive and would be easy for Claude to correctly select from a large pool of skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Audit Xcode project configuration, build settings, scheme behavior, and script phases' and 'find build-time improvements with explicit approval gates.' These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (audit Xcode project configuration, build settings, scheme behavior, script phases for build-time improvements) and 'when' with an explicit 'Use when...' clause listing seven specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'Xcode project', 'build settings', 'slow incremental builds', 'target dependencies', 'run script phase', 'parallelization', 'module-map', 'DEFINES_MODULE', 'build analysis'. These are terms developers naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Xcode project-level build configuration auditing. The combination of Xcode-specific terms like 'scheme behavior', 'DEFINES_MODULE', 'run script phase', and 'module-map' makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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, domain-specific skill that efficiently communicates what to audit in Xcode projects without over-explaining concepts Claude already knows. Its main weakness is the lack of executable commands or concrete code examples for performing the audit steps, and the absence of a clearly sequenced workflow with validation checkpoints. The progressive disclosure and reference structure are excellent.
Suggestions
Add a sequenced workflow section (e.g., 'Step 1: Run `xcodebuild -showBuildTimingSummary` to collect timing data, Step 2: Compare build settings with `xcodebuild -showBuildSettings`...') with explicit validation checkpoints between steps.
Include concrete, executable commands for common audit tasks such as extracting build settings, generating build timing summaries, or checking scheme configurations (e.g., `xcodebuild -scheme <name> -showBuildSettings | grep SWIFT_WHOLE_MODULE_OPTIMIZATION`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Xcode, build settings, or schemes are—it assumes Claude already knows these concepts. Every bullet point adds specific, non-obvious domain knowledge (e.g., 'Planning Swift module' time, ExtractAppIntentsMetadata, Task Backtraces). No padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides specific things to look for and concrete reporting requirements, but lacks executable commands or code examples. There are no concrete xcodebuild commands, no example build timing summary parsing, and no copy-paste ready snippets for extracting or analyzing build settings. The guidance is specific but descriptive rather than executable. | 2 / 3 |
Workflow Clarity | The skill describes what to review and how to report findings, but lacks a clear sequenced workflow with explicit steps (e.g., Step 1: run this, Step 2: check that). The approval gate is mentioned as a core rule but not integrated into a step-by-step process. For a multi-step audit process involving destructive changes (modifying project files), the absence of explicit validation checkpoints and a clear sequence caps this at 2. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with a clear overview in the SKILL.md and well-signaled one-level-deep references to four separate reference files (build-settings-best-practices.md, project-audit-checks.md, recommendation-format.md, build-optimization-sources.md) plus a cross-skill handoff to spm-build-analysis. Navigation is clear and references are appropriately organized. | 3 / 3 |
Total | 10 / 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.
- Commit
6bd7b59
- 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.