spm-build-analysis
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.
89
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 specific niche (SPM/Xcode build performance analysis), lists concrete capabilities, and provides comprehensive trigger terms in an explicit 'Use when...' clause. The description is well-structured, uses third person voice, and covers both common and edge-case scenarios a developer might describe when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyze dependencies, package plugins, module variants, CI-oriented build overhead. Also mentions specific sub-tasks like duplicate module builds, circular dependencies, module splitting, and modularization best practices. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyze SPM dependencies, plugins, module variants, CI build overhead) and 'when' with an explicit 'Use when...' clause listing numerous specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'SPM slowness', 'package resolution time', 'build plugin overhead', 'Xcode builds', 'clean or incremental build performance', 'circular dependencies', 'modularization', 'Swift Package Manager'. These are all terms developers naturally use when experiencing these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Swift Package Manager build performance in Xcode. The combination of SPM, Xcode builds, package plugins, and module-level analysis creates a clear, narrow domain unlikely to conflict with general build or dependency 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 strong, domain-specific skill that provides genuinely useful knowledge Claude wouldn't have by default—particularly around SPM verification steps, modular SDK migration trade-offs, and macro rebuild cascading. Its main weakness is the lack of an explicit end-to-end workflow sequence; the content reads more like a reference document than a step-by-step procedure. Some sections in Focus Areas could be tightened for conciseness.
Suggestions
Add a numbered top-level workflow (e.g., '## Workflow: 1. Gather evidence → 2. Verify package linkage → 3. Analyze focus areas → 4. Report findings → 5. Hand off if needed') to make the overall sequence explicit and improve workflow clarity.
Tighten the Focus Areas bullet list—several items (e.g., swift-syntax universal builds, multi-platform build multiplication) include explanatory context that could be condensed into shorter, more directive statements.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and covers domain-specific knowledge Claude wouldn't inherently know, but some sections are verbose—particularly the 'Modular SDK Migration Caveat' and 'Focus Areas' bullet list could be tightened. Several bullet points in Focus Areas explain concepts at a level that could be more concise. | 2 / 3 |
Actionability | The skill provides concrete, executable guidance: specific files to inspect (Package.swift, project.pbxproj), exact keys to search for (XCLocalSwiftPackageReference, XCSwiftPackageProductDependency), a helper script command, and a clear reporting format with required fields. The verification steps are copy-paste actionable. | 3 / 3 |
Workflow Clarity | While individual sections are clear, the overall workflow sequence is implicit rather than explicit—there's no numbered end-to-end process showing the order of operations (inspect → verify → analyze → report → hand off). The verification section has good validation steps, but the skill lacks a clear top-level sequenced workflow tying all sections together, and there are no explicit feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to a detailed audit checklist, recommendation format, and source citations. Cross-references to sibling skills (xcode-project-analyzer, xcode-compilation-analyzer) are clearly signaled with relative links. Content is appropriately split between the main skill and reference files. | 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.