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
Pending
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 an excellent skill description that clearly defines its scope (Xcode build configuration auditing), lists specific concrete actions, and provides a comprehensive 'Use when' clause with multiple 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 project configuration, build settings, scheme behavior, script phases, find build-time improvements, with explicit approval gates. Very detailed about what it does. | 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 experiencing build performance issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Xcode project-level build configuration auditing. The combination of Xcode-specific terminology (scheme behavior, script phases, DEFINES_MODULE, 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 with good progressive disclosure to reference materials. Its main weakness is the lack of concrete executable examples (specific xcodebuild commands, example output parsing) and an explicit step-by-step audit workflow with validation checkpoints. The content is highly knowledgeable but reads more as a checklist of concerns than a guided procedure.
Suggestions
Add a numbered step-by-step audit workflow (e.g., 1. Run `xcodebuild -showBuildTimingSummary` 2. Check scheme settings 3. Compare build settings against checklist 4. Report findings) with explicit validation checkpoints between phases.
Include at least one concrete example of a finding report using the reporting format described, showing evidence, scope, impact, and approval requirement filled in with realistic Xcode data.
Add specific executable commands for gathering build timing data, such as `xcodebuild -buildWithTimingSummary` or how to enable Build Timing Summary in Xcode, rather than just referencing what to look for in the output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every bullet point adds specific, non-obvious domain knowledge about Xcode build analysis. There's no explanation of what Xcode is or how builds work — it assumes Claude's competence and focuses on actionable audit items like 'Planning Swift module' time, ExtractAppIntentsMetadata, and Task Backtraces. | 3 / 3 |
Actionability | The skill provides specific things to look for (e.g., zero-change build overhead, script input/output declarations, DEFINES_MODULE settings) and concrete reporting requirements, but lacks executable commands or code examples. There are no specific xcodebuild commands, no example build timing summary parsing, and no concrete examples of what a finding report looks like. | 2 / 3 |
Workflow Clarity | The skill describes what to review and how to report but doesn't provide a clear sequenced workflow with validation checkpoints. The audit process is implied (review settings → compare against best practices → report findings → get approval) but not explicitly ordered. The approval gate is mentioned but not integrated into a step-by-step flow. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the SKILL.md and well-signaled one-level-deep references to build-settings-best-practices.md, project-audit-checks.md, recommendation-format.md, and build-optimization-sources.md. The handoff to spm-build-analysis is also clearly signaled with context for when to use it. | 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
b599058
- 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.