CtrlK
BlogDocsLog inGet started
Tessl Logo

migration-refactor-specialist

Skill para migracoes, modernizacao de legacy e refactors estruturais. Use quando precisar fazer upgrades grandes, extracao incremental, strangler pattern, compatibilidade de transicao e rollout seguro. Trigger em: "migracao de framework", "modernizacao de legacy", "strangler pattern", "refactor estrutural", "upgrade grande", "extracao incremental", "migracao de runtime", "trocar ORM", "rollout incremental de refactor", "migrar para", "spring boot 3", "spring boot 2 para 3", "jakarta migration", "javax para jakarta", "openrewrite", "upgrade spring boot", "migrar jdk 21", "jdk 21 upgrade", "java 21 migration", "spring boot upgrade", "spring 3 migration".

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/23-migration-refactor-specialist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and concise with a notably concrete Delete-List Review section, but its core migration workflow and progressive-disclosure references depend on bundle files (playbooks/, templates/, policies/) that are not actually present, weakening both actionability and navigation.

Suggestions

Ship the referenced bundle files (playbooks/spring-boot-2-to-3.md, playbooks/references/*.md, templates/migration-plan.md) or inline the minimal migration steps so the skill is self-contained.

Add an explicit sequenced migration workflow with validation checkpoints (e.g., run tests per phase, confirm rollback before next phase) rather than only checklists.

Verify that policies/*.md and GLOBAL.md references resolve to real files, or drop references the skill does not actually depend on.

DimensionReasoningScore

Conciseness

The body is lean and list-driven, assumes Claude's competence, and does not re-explain concepts Claude already knows; only minor phrasing could be tightened, sitting just below the 'lean and efficient' anchor of 5.

4 / 5

Actionability

The Delete-List Review section gives concrete guidance (5 categories, 'cite arquivo:linha', evidence requirements) but the core migration execution defers to 'playbooks/spring-boot-2-to-3.md' which is referenced but not present in the bundle, leaving key execution details incomplete.

3 / 5

Workflow Clarity

Checklists (Checklist Base, Evidencia de Conclusao) provide rough structure and mention 'validacao incremental por fase' and 'rollback', but there is no explicit sequenced workflow with validation checkpoints in the body — the concrete steps live in the absent playbook, matching the 'steps listed but checkpoints implicit' anchor at 3.

3 / 5

Progressive Disclosure

Section structure and one-level-deep signaling (playbook table, references list) are good, but the referenced bundle files (playbooks/, templates/migration-plan.md, policies/, GLOBAL.md) do not exist in the bundle, so navigation points to missing material — more than the 'minor organization gaps' allowed at 4.

3 / 5

Total

13

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with comprehensive trigger terms, explicit what/when guidance, and a distinct niche. The only weakness is second-person imperative voice ('Use quando') which costs one specificity point per the voice guideline.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('extracao incremental', 'strangler pattern', 'compatibilidade de transicao', 'rollout seguro'), matching the 'several specific actions' anchor at 4, but the imperative 'Use quando' is second-person voice which per the guidelines reduces specificity by one.

3 / 5

Completeness

Explicitly answers both 'what' (migracoes, modernizacao de legacy, refactors estruturais) and 'when' ('Use quando precisar...' plus a concrete 'Trigger em' list), matching the anchor for clearly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive trigger list covering natural phrases users would say ('migrar para', 'trocar ORM', 'upgrade spring boot') plus synonyms and version-specific terms ('spring boot 2 para 3', 'javax para jakarta', 'jdk 21 upgrade').

5 / 5

Distinctiveness Conflict Risk

Clear niche of large migrations/refactors with distinct, specific triggers (jakarta migration, OpenRewrite, JDK 21) that are unlikely to fire for unrelated skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
felvieira/claude-skills-fv
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.