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.
55
Quality
44%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/23-migration-refactor-specialist/SKILL.mdQuality
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 adequately covers the 'what' and 'when' aspects with an explicit 'Use quando' clause, which is a strength. However, it lacks specific concrete actions and relies on somewhat abstract concepts. The mixed Portuguese/English terminology may reduce trigger effectiveness for users searching in either language consistently.
Suggestions
Add specific concrete actions like 'Creates migration plans', 'Extracts modules incrementally', 'Generates compatibility adapters' to improve specificity
Expand trigger terms to include common variations in a consistent language: 'legacy code', 'technical debt', 'version upgrade', 'framework migration', 'codebase modernization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (migrations, legacy modernization, structural refactors) and mentions some patterns (strangler pattern, incremental extraction), but lacks concrete actions like 'extract modules', 'create compatibility layers', or 'generate migration scripts'. | 2 / 3 |
Completeness | Explicitly answers both what (migrations, modernization, structural refactors) and when ('Use quando precisar fazer upgrades grandes, extracao incremental, strangler pattern, compatibilidade de transicao e rollout seguro'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'upgrades grandes', 'strangler pattern', 'rollout seguro', but mixes Portuguese and English inconsistently, and misses common variations users might say like 'legacy code', 'migration plan', 'refactoring', 'technical debt'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on migrations and legacy modernization provides some distinctiveness, but terms like 'refactors estruturais' could overlap with general refactoring skills, and 'upgrades grandes' is somewhat vague. | 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 process definition document than actionable guidance for Claude. It defines what a migration specialist should produce but provides no concrete examples, no step-by-step workflow, and no executable guidance. For a high-risk domain like migrations, the absence of validation checkpoints and rollback procedures in actionable form is a significant gap.
Suggestions
Add a concrete example migration workflow with numbered steps, validation checkpoints, and explicit rollback triggers (e.g., 'Step 3: Run compatibility tests. If >5% failures, execute rollback procedure X')
Include at least one concrete example showing input state, migration plan output format, and phase structure - even a simplified template would help
Replace or supplement the abstract checklist with an executable sequence that shows when to validate, what commands to run, and how to verify each phase before proceeding
Add specific examples of 'estrategia de compatibilidade temporaria' patterns (e.g., feature flags, adapter pattern, strangler fig) with code snippets showing implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is reasonably efficient but includes some redundancy between 'Saidas Esperadas', 'Checklist Base', and 'Evidencia de Conclusao' sections which overlap significantly. The governance references add value but could be more compact. | 2 / 3 |
Actionability | The skill provides abstract guidance without concrete examples, commands, or executable steps. It describes what should happen ('plano incremental', 'estrategia de compatibilidade') but never shows how to actually do it - no code, no specific commands, no example migration plans. | 1 / 3 |
Workflow Clarity | Despite being a migration skill where workflow is critical, there's no clear sequence of steps. The checklist items are unordered requirements, not a workflow. No validation checkpoints, no feedback loops for error recovery, no explicit phase sequencing. | 1 / 3 |
Progressive Disclosure | References to external policies and templates are present and one-level deep, which is good. However, the skill itself lacks a quick-start section and the references are not clearly signaled with descriptions of what each contains. | 2 / 3 |
Total | 6 / 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.
- Repository
- felvieira/claude-skills-fv
- Commit
524725e
- 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.