Migrates a Spring MVC application to Spring Boot, converting XML config to auto-configuration, restructuring the project, and replacing container deployment with embedded. Use when modernizing a legacy Spring app, when moving off a standalone servlet container, or when the user has web.xml and wants application.yml.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill spring-mvc-to-boot-migrator97
Quality
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 articulates the specific migration task, uses appropriate technical terminology that users would naturally employ, and provides explicit trigger conditions. The description effectively distinguishes itself from general Spring or Java skills by focusing on the specific MVC-to-Boot migration scenario with concrete file format references.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'converting XML config to auto-configuration', 'restructuring the project', and 'replacing container deployment with embedded'. These are precise technical operations. | 3 / 3 |
Completeness | Clearly answers both what ('Migrates a Spring MVC application to Spring Boot, converting XML config...') AND when ('Use when modernizing a legacy Spring app, when moving off a standalone servlet container, or when the user has web.xml and wants application.yml'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Spring MVC', 'Spring Boot', 'XML config', 'legacy Spring app', 'servlet container', 'web.xml', 'application.yml'. Good coverage of both framework names and file types. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Spring MVC to Spring Boot migration specifically. The combination of 'web.xml', 'application.yml', 'servlet container', and 'auto-configuration' creates distinct triggers unlikely to conflict with general Java or Spring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent migration skill that provides concrete, incremental guidance for a complex task. The content is highly actionable with executable code, clear workflow steps with validation checkpoints, and practical gotcha tables. Minor improvement opportunity in splitting some reference content into separate files for better progressive disclosure.
Suggestions
Consider moving the 'Common XML → Boot mappings' table to a separate MAPPINGS.md reference file, keeping just the most common 2-3 in the main skill
The 'Gotchas' table could be a separate GOTCHAS.md file linked from the main skill for easier maintenance and discovery
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient content that assumes Claude's competence with Spring. No unnecessary explanations of what Spring MVC or Boot are - jumps straight to actionable migration guidance. Tables compress information effectively. | 3 / 3 |
Actionability | Provides fully executable code examples for pom.xml, main class, @Configuration beans, and application.yml. The XML-to-Boot mappings table gives concrete, copy-paste ready transformations. | 3 / 3 |
Workflow Clarity | Clear 4-step migration sequence with explicit validation checkpoints ('Verify everything works before touching XML', 'Run tests'). The incremental approach with @ImportResource bridge ensures the app stays running at every step. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and tables, but this is a substantial document (~200 lines) that could benefit from splitting detailed mappings or gotchas into separate reference files. The output format section could be a template file. | 2 / 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.
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.