xcode-compilation-analyzer
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
95
93%
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 a narrow, well-scoped domain (Swift compilation performance analysis), lists concrete actions, and provides a comprehensive 'Use when' clause with multiple natural trigger terms. It uses proper third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics' and 'produce a recommend-first source-level optimization plan.' These are detailed, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyze compile hotspots using build timing summaries and diagnostics, produce optimization plan) and 'when' (explicit 'Use when...' clause listing six distinct trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'slow compilation', 'type-checking warnings', 'clean-build compile phases', 'CompileSwiftSources tasks', 'warn-long-function-bodies', 'speed up Swift type checking'. These are highly specific and natural phrases developers would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting Swift compilation performance specifically. Terms like 'CompileSwiftSources', 'warn-long-function-bodies', and 'Swift frontend diagnostics' are unique enough to avoid conflicts with general code optimization or other language-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, expert-level skill that provides specific, actionable guidance for Swift compilation analysis. Its strengths are excellent conciseness (no wasted tokens), deep domain-specific actionability (exact flags, thresholds, patterns), and good progressive disclosure to reference files. The main weakness is the workflow section, which lacks explicit validation/feedback loops for verifying that recommendations actually improve build times.
Suggestions
Add a verification step to the analysis workflow, e.g., 'After applying a recommendation, re-run the diagnostics script and compare timing summaries to confirm improvement before proceeding to the next change.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Xcode, Swift, or compilation are. Every section provides specific, non-obvious information—diagnostic flags, timing categories, threshold values, and nuanced guidance about wall-clock vs cumulative impact. No padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete diagnostic flags with exact syntax, a runnable script invocation with specific arguments, specific patterns to look for (e.g., 'SwiftEmitModule time can reach 60s+'), and a clear reporting format. The Apple-Derived Checks section gives specific, actionable code-level patterns rather than vague advice. | 3 / 3 |
Workflow Clarity | The 5-step analysis workflow provides a clear sequence, and the reporting format includes validation-like elements (confidence, evidence). However, there are no explicit validation checkpoints or feedback loops—e.g., no step to verify that a recommended change actually improved compile time, and no guidance on what to do if diagnostics produce unexpected or ambiguous results. | 2 / 3 |
Progressive Disclosure | The skill provides a well-structured overview with clear sections, and appropriately references three external files (code-compilation-checks.md, recommendation-format.md, build-optimization-sources.md) for detailed content. It also cross-references the xcode-project-analyzer skill for project-level issues. All references are one level deep and clearly signaled. | 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.