xcode-build-fixer
Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level compilation fixes, or SPM restructuring that was recommended by an analysis skill.
94
92%
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 a strong skill description that clearly articulates specific concrete actions (applying build settings, script phase guards, SPM restructuring, re-benchmarking), includes natural developer-facing trigger terms, and explicitly defines both what the skill does and when to use it. The reference to the upstream 'xcode-build-orchestrator' skill effectively positions this as a distinct implementation step in a workflow, reducing conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: applying build optimization changes, re-benchmarking, implementing build setting changes, script phase guards, source-level compilation fixes, and SPM restructuring. | 3 / 3 |
Completeness | Clearly answers both 'what' (apply approved Xcode build optimization changes and re-benchmark) and 'when' (explicit 'Use when' clause covering approved optimization plans, specific build fixes, build setting changes, script phase guards, source-level compilation fixes, and SPM restructuring). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'Xcode', 'build optimization', 'build fixes', 'build setting changes', 'script phase guards', 'compilation fixes', 'SPM restructuring', 'benchmark'. These are terms developers naturally use when discussing Xcode build performance. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: it specifically handles the *application* of approved Xcode build optimizations from a named upstream skill (xcode-build-orchestrator), distinguishing it from analysis/diagnosis skills. The mention of the prerequisite skill and specific implementation actions makes it unlikely to conflict. | 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 well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. Its main weakness is verbosity — the regression evaluation and reporting sections contain substantial philosophical guidance and justification that could be condensed without losing clarity. The domain-specific content (build settings, SPM restructuring, script phase fixes) is genuinely valuable and well-organized.
Suggestions
Condense the 'Evaluating Regressions' and 'Best-practice settings are not revert candidates' sections by ~40% — much of the reasoning and justification (e.g., 'Apple is actively investing in this') is unnecessary context for Claude and could be reduced to concise rules.
The 'Reporting' section has overlapping guidance with the 'Execution Report' template — consolidate into a single reporting section to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~200+ lines) and includes substantial explanation of regression evaluation philosophy, best-practice justifications, and nuanced reporting guidance that could be more concise. Sections like 'Evaluating Regressions' and 'Best-practice settings are not revert candidates' are verbose with rationale Claude could infer. However, much of the domain-specific guidance (pbxproj editing, SPM restructuring) genuinely adds value Claude wouldn't know. | 2 / 3 |
Actionability | The skill provides concrete, specific guidance throughout: exact build setting names and values, specific bash commands for benchmarking, specific verification commands (xcodebuild -showBuildSettings, xcodebuild -resolvePackageDependencies), concrete script phase guard syntax, and detailed before/after patterns referenced via fix-patterns.md. The benchmark command is copy-paste ready. | 3 / 3 |
Workflow Clarity | The execution workflow is clearly sequenced (6 steps) with explicit validation checkpoints: compile verification after each change (step 4), re-benchmark after all changes (step 5), and comparison/reporting (step 6). The SPM section includes a pre-validation step (git ls-remote, xcodebuild -resolvePackageDependencies). Regression evaluation includes clear feedback loops for revert decisions. The execution report template provides a structured checklist. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear one-level-deep references to detailed materials: fix-patterns.md, build-settings-best-practices.md, recommendation-format.md. Cross-skill escalation paths are clearly signaled. The main content stays at the right level of abstraction while pointing to specifics elsewhere. | 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.
- 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.