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.

Quality

44%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/23-migration-refactor-specialist/SKILL.md

Quality

Discovery

67%

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

The description has a clear structure with both 'what' and 'when' clauses, which is its strongest aspect. However, it stays at a conceptual level without listing concrete actions the skill performs, and the trigger terms, while relevant, could be more comprehensive with specific technology names and common user phrasings. The Portuguese language may also limit discoverability for non-Portuguese users.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates adapter layers, generates migration scripts, builds feature flags for incremental rollout'

Expand trigger terms with more natural variations users might say, such as 'upgrade framework version', 'replace legacy module', 'backward compatibility', 'phased migration', 'deprecate old system'

Dimension	Reasoning	Score
Specificity	Names the domain (migrations, legacy modernization, structural refactors) and mentions some patterns (strangler pattern, incremental extraction), but doesn't list concrete actions like 'extract module X', 'create adapter layers', or 'generate migration scripts'. The terms are more conceptual than actionable.	2 / 3
Completeness	Explicitly answers both 'what' (migrations, legacy modernization, structural refactors) and 'when' with a clear 'Use quando precisar fazer...' clause listing specific trigger scenarios like upgrades, incremental extraction, strangler pattern, transition compatibility, and safe rollout.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'migracoes', 'legacy', 'refactors', 'strangler pattern', 'upgrades grandes', and 'rollout seguro'. However, it misses common natural variations users might say such as 'migrate database', 'upgrade framework', 'deprecate old code', 'backward compatibility', or specific technology terms. The Portuguese language also limits trigger matching for English-speaking users.	2 / 3
Distinctiveness Conflict Risk	Terms like 'refactors estruturais' and 'modernizacao de legacy' carve out a reasonable niche, but 'refactors' could overlap with general code refactoring skills, and 'upgrades grandes' is broad enough to conflict with dependency update or version upgrade skills. The strangler pattern mention adds some distinctiveness.	2 / 3
	Total	9 / 12 Passed

Implementation

22%

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

This skill reads more like a role description or process checklist than actionable guidance for performing migrations. It lacks any concrete techniques, code examples, or step-by-step workflows for strangler pattern implementation, incremental extraction, compatibility layers, or rollback procedures. The content is almost entirely abstract, telling Claude what outcomes to produce without showing how to achieve them.

Suggestions

Add a concrete, sequenced workflow for a typical migration (e.g., 1. Audit current state → 2. Define compatibility layer → 3. Implement strangler pattern → 4. Validate phase → 5. Cut over) with explicit validation checkpoints at each phase.

Include at least one concrete example of a migration pattern (e.g., strangler fig with code showing how to route between old and new implementations, or a database migration with rollback SQL).

Replace or supplement the abstract checklists with executable guidance—specific commands, file templates, or decision trees that Claude can directly apply rather than interpret.

Consolidate the overlapping sections (Saidas Esperadas, Checklist Base, Evidencia de Conclusao) which all mention similar items like rollback criteria and phase tracking.

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but contains redundancy between sections (e.g., 'Saidas Esperadas', 'Checklist Base', and 'Evidencia de Conclusao' overlap significantly with repeated mentions of rollback, phases, and risks). Some sections like 'Quando Usar/Nao Usar' are efficient, but overall it could be tightened.	2 / 3
Actionability	The skill provides no concrete commands, code examples, executable steps, or specific techniques. It describes what should happen at an abstract level ('plano incremental', 'estrategia de compatibilidade temporaria') without showing how to actually do any of it. There are no strangler pattern examples, no migration script templates, no concrete rollback procedures.	1 / 3
Workflow Clarity	There is no sequenced workflow for performing a migration. The checklist and outputs are stated as bullet points of desired outcomes, not as ordered steps with validation checkpoints. For a skill dealing with high-risk, multi-step migration operations, the absence of a clear phased workflow with explicit validation gates is a significant gap.	1 / 3
Progressive Disclosure	The skill references external policies and a migration plan template, which is good progressive disclosure structure. However, the references are numerous and not clearly signaled with descriptions of what each contains. The main content itself lacks substance to serve as a useful overview, making the references feel like the skill is deferring all real content elsewhere.	2 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: felvieira/claude-skills-fv
Commit: d87ad31

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.