springboot-migration
Migrates Spring Boot applications to Boot 4 with Java 25, including related Spring Modulith 2 and Testcontainers 2 upgrade work. Use when the task is a concrete upgrade, dependency transition, starter rename, test-annotation migration, or phased migration plan. Do not use for greenfield project creation or for isolated repository design questions.
92
85%
Does it follow best practices?
Impact
94%
2.29xAverage score across 8 eval scenarios
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 its scope, provides rich trigger terms, and explicitly states both when to use and when not to use the skill. The inclusion of specific technologies (Spring Boot 4, Java 25, Spring Modulith 2, Testcontainers 2) and concrete action types (dependency transition, starter rename, test-annotation migration) makes it highly actionable and distinguishable. The 'Do not use' clause is a particularly strong addition for reducing false matches.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'dependency transition, starter rename, test-annotation migration, phased migration plan' alongside the core migration from Spring Boot to Boot 4 with Java 25, Spring Modulith 2, and Testcontainers 2. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrates Spring Boot apps to Boot 4 with Java 25, including Modulith 2 and Testcontainers 2 upgrades) and 'when' (explicit 'Use when' clause with concrete triggers, plus a 'Do not use' clause that further clarifies boundaries). | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms users would say: 'Spring Boot', 'Boot 4', 'Java 25', 'Spring Modulith 2', 'Testcontainers 2', 'upgrade', 'dependency transition', 'starter rename', 'migration'. These cover the key terms a developer would use when requesting this kind of work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Spring Boot 4 migration specifically. The explicit exclusions ('not for greenfield project creation or isolated repository design questions') further reduce conflict risk with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%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 migration skill with excellent workflow clarity and progressive disclosure—the phased approach with scan-first methodology and clear reference file navigation is strong. Its main weakness is that the core migration phases (1-3) lack concrete code examples or specific commands, making the actionability dependent on external reference files. Minor redundancy between the reference table and the reference loading guide section slightly hurts conciseness.
Suggestions
Add at least one concrete code example per phase (e.g., a before/after for a starter rename in Phase 1, an import migration in Phase 2, a property change in Phase 3) to improve actionability without requiring reference file loading for simple cases.
Remove the 'Reference loading guide' section since it duplicates the table in Step 2, or consolidate them into a single location to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy—the reference loading guide section repeats the table from Step 2, and some phrasing could be tightened (e.g., the Purpose section restates what the workflow already demonstrates). However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The scanner command is concrete and executable, and the output format template is helpful. However, the actual migration steps in Phases 1-4 are high-level checklists ('update imports and package names', 'fix Jackson 3 issues') without concrete code examples or specific commands, relying entirely on external reference files for the real details. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit phases, a defined migration order for mixed upgrades, verification as a dedicated phase, and a stop-on-failure rule. The progress reporting step after each phase creates a feedback loop. The phased approach with scan-first, plan, execute, verify is well-structured. | 3 / 3 |
Progressive Disclosure | The skill cleanly separates the overview workflow from detailed migration content in reference files, with a clear table mapping triggers to specific reference documents. References are one level deep and well-signaled. The structure makes it easy to load only relevant references. | 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
efa5546
- 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.