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 capabilities (applying build setting changes, script phase guards, source-level compilation fixes, SPM restructuring, re-benchmarking), provides explicit trigger guidance via a 'Use when' clause, and distinguishes itself from the analysis/orchestration skill by focusing on the implementation phase. It uses third person voice consistently and includes domain-specific trigger terms that developers would naturally use.
| 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 optimization changes, re-benchmark to verify improvement) and 'when' (explicit 'Use when' clause covering approved optimization plan from xcode-build-orchestrator, applying specific build fixes, implementing various types of changes recommended by an analysis skill). | 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 Xcode build optimizations that were previously approved by a named orchestrator skill (xcode-build-orchestrator), clearly distinguishing it from analysis/diagnosis skills. The scope is narrow and well-defined. | 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 clear workflows, validation checkpoints, and good progressive disclosure to reference materials. Its main weakness is verbosity — the regression evaluation section and reporting guidance could be significantly tightened without losing clarity, as several paragraphs explain reasoning and philosophy rather than providing instructions. Despite the length, the domain-specific content (Xcode build settings, SPM restructuring patterns) is genuinely useful knowledge Claude wouldn't have.
Suggestions
Condense the 'Evaluating Regressions' section by converting the prose explanations into a concise decision table or flowchart (e.g., 'If only cold clean build slower but cached/incremental faster → keep; if all build types slower → revert speculative changes').
Trim the 'Best-practice settings are not revert candidates' subsection — the list of settings with justifications could be a simple bullet list without the explanatory commentary after each item, since the rationale is already covered by the umbrella statement.
| 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. The 'Evaluating Regressions' section in particular is verbose with reasoning Claude could infer. However, much of the content is domain-specific knowledge Claude wouldn't inherently know (Xcode build settings, compilation cache trade-offs), so it's not purely padding. | 2 / 3 |
Actionability | The skill provides specific build settings with exact values (e.g., `DEBUG_INFORMATION_FORMAT = dwarf`), concrete bash commands for benchmarking, specific file paths (`project.pbxproj`, `.build-benchmark/optimization-plan.md`), and executable script phase guards. The fix categories include precise, copy-paste-ready patterns and verification commands like `xcodebuild -showBuildSettings`. | 3 / 3 |
Workflow Clarity | The execution workflow is clearly sequenced (6 steps) with explicit validation checkpoints: compile verification after each change, re-benchmark after all changes, and a clear feedback loop for regressions (evaluate, flag, potentially revert). The SPM section includes pre-validation steps (git ls-remote, xcodebuild -resolvePackageDependencies). The execution report template provides a structured checklist for the complete process. | 3 / 3 |
Progressive Disclosure | The skill maintains a clear overview structure with well-signaled one-level-deep references to detailed materials: fix-patterns.md, build-settings-best-practices.md, recommendation-format.md, and cross-skill escalation paths. The main content stays at the right level of detail for an overview 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
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.