CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

legacy-modernizer

Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use for legacy system updates, framework migrations, or technical debt reduction.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/legacy-modernizer/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.

A short, well-organized overview that names the right domain concepts and migration examples but stays at the principle level throughout. Its main weaknesses are generic filler sections, the absence of any executable commands or procedures, and a workflow with no explicit validation checkpoints despite covering risky refactoring operations.

Suggestions

Delete the 'Use this skill when', 'Do not use this skill when', and 'Instructions' sections along with the 'You are a legacy modernization specialist' line — they restate the frontmatter description or state generic behavior Claude already follows, and add no domain value.

Add at least a few executable anchors to the Approach section, e.g. concrete commands for dependency auditing or a skeleton compatibility-shim/adapter pattern, so guidance moves from principles to steps Claude can run.

Turn the Approach list into a real sequenced workflow with validation checkpoints (e.g. 'run existing test suite and record baseline before refactoring; only proceed when green; re-run after each phase'), since the skill explicitly covers risky changes to working legacy systems.

DimensionReasoningScore

Conciseness

The domain sections (Focus Areas, Approach, Output) are lean and token-efficient, but roughly a third of the body is removable boilerplate: 'Working on legacy modernizer tasks or workflows', 'Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.', and 'You are a legacy modernization specialist...'. Not 2 because the core content carries no concept explanations; not 4 because three entire sections add nothing Claude doesn't already know.

3 / 5

Actionability

Concrete specifics exist ('jQuery→React, Java 8→17, Python 2→3', 'Strangler fig pattern - gradual replacement', 'Compatibility shim/adapter layers'), but the guidance contains no code, commands, or procedures for executing any step. Not 4 because nothing is executable or copy-paste ready; not 2 because Focus Areas and Output name concrete, specific artifacts rather than pure high-level hints.

3 / 5

Workflow Clarity

The Approach section lists a numbered sequence ('1. Strangler fig pattern... 2. Add tests before refactoring... 5. Feature flags for gradual rollout') but the steps are principles rather than operations, and validation is only the generic 'Apply relevant best practices and validate outcomes.' Legacy refactoring is a risky, functionality-changing context, so the missing-validation cap of 3 applies. Not 4 because no explicit checkpoints exist despite 'Rollback procedures for each phase' being listed as an output; not 2 because the tests-first, incremental ordering is coherent.

3 / 5

Progressive Disclosure

The body is 43 lines with clean, well-organized sections (Focus Areas, Approach, Output) and no bundle files exist, so no external references are needed. The simple-skill exception applies: under 50 lines with well-organized sections and no nested references.

5 / 5

Total

14

/

20

Passed

Description

88%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 that clearly states concrete capabilities and provides an explicit, well-phrased 'Use for...' trigger clause. Keyword coverage is good though missing a few natural synonyms, and there is minor overlap risk with general refactoring or dependency-update skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Refactor legacy codebases, migrate outdated frameworks', 'Handles technical debt, dependency updates, and backward compatibility' — with comprehensive coverage of the modernization domain. Not 4 because no meaningful capability gaps remain; the verbs and objects are as concrete as the anchor-5 example.

5 / 5

Completeness

Both questions are answered explicitly: the opening sentences state what the skill does, and 'Use for legacy system updates, framework migrations, or technical debt reduction' gives concrete trigger phrases. This matches the anchor-5 example structure exactly; not 4 because the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'legacy system updates, framework migrations, or technical debt reduction', plus 'outdated frameworks' and 'backward compatibility' — phrases users would actually say. Not 5 because common synonyms like 'upgrade', 'end-of-life', or named stack migrations are missing; not 3 because coverage clearly exceeds the single-phrase anchor-3 example.

4 / 5

Distinctiveness Conflict Risk

The legacy-modernization niche ('legacy codebases', 'technical debt', 'gradual modernization') is mostly distinct with clear triggers. Not 5 because a generic refactoring or dependency-update skill would still overlap on terms like 'refactor' and 'dependency updates'; not 3 because the legacy/debt framing is far more specific than the anchor-3 example.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/legacy-modernizer/SKILL.md

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.