Migrate KMP projects from CocoaPods (kotlin("native.cocoapods")) to Swift Package Manager (swiftPMDependencies DSL) — replaces pod() with package(), transforms cocoapods.* imports to swiftPMImport.*, and reconfigures the Xcode project.
87
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
82%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, technically precise description that clearly identifies a specific migration task with concrete actions. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical specificity and distinctive terminology make it excellent for disambiguation.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when migrating KMP projects from CocoaPods to SPM, or when the user mentions cocoapods migration, SPM conversion, or swiftPMDependencies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'replaces pod() with package()', 'transforms cocoapods.* imports to swiftPMImport.*', and 'reconfigures the Xcode project'. These are precise, technical operations. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed migration steps, but lacks an explicit 'Use when...' clause. The when is implied (migrating from CocoaPods to SPM) but not explicitly stated as trigger guidance. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms: 'KMP', 'CocoaPods', 'Swift Package Manager', 'swiftPMDependencies', 'pod()', 'package()', 'Xcode project'. Users migrating would naturally use these exact terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: KMP + CocoaPods to SPM migration is a very specific use case. The combination of 'kotlin("native.cocoapods")', 'swiftPMDependencies DSL', and specific function replacements makes conflicts extremely unlikely. | 3 / 3 |
Total | 11 / 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 high-quality, comprehensive migration skill with excellent workflow clarity and actionability. The 8-phase structure with explicit validation checkpoints and clear sequencing makes complex operations manageable. Minor verbosity in explanatory sections could be trimmed, but the content is largely well-justified given the migration's complexity and potential for errors.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what linkOnly means, what products vs importedModules are). Some sections could be tightened, though most content is necessary for this complex migration. | 2 / 3 |
Actionability | Excellent actionability with executable bash commands, specific Kotlin code snippets, regex patterns for bulk replacement, and concrete examples throughout. Commands are copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | Outstanding 8-phase workflow with explicit validation checkpoints (Phase 7), clear sequencing, and critical warnings about order (keep CocoaPods until Phase 6). Includes feedback loops for error recovery and explicit 'If X fails' guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview table, phased approach, and appropriate delegation to reference files (dsl-reference.md, common-pods-mapping.md, troubleshooting.md, cocoapods-extras-patterns.md). 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.
4ba5e0c
Table of Contents
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.