CtrlK
BlogDocsLog inGet started
Tessl Logo

framework-migration-legacy-modernize

Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through ex

53

Quality

58%

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/framework-migration-legacy-modernize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable with a well-sequenced, safeguarded multi-phase workflow, but it is padded with an unnecessary concept explainer and boilerplate, and it is monolithic with no progressive disclosure into reference files.

Suggestions

Delete the '[Extended thinking: ...]' paragraph and the generic 'Instructions' section — both explain concepts Claude already knows or restate obvious process boilerplate.

Extract the per-phase subagent prompts into reference files (e.g., references/phase1-assessment.md) and link to them from a lean overview, so SKILL.md acts as a navigation hub.

Add explicit 'validate output before proceeding to next phase' checkpoints between phases to lift workflow clarity, even though rollback/decommission safeguards already exist.

DimensionReasoningScore

Conciseness

Noticeably verbose: the '[Extended thinking: ...]' paragraph explains the strangler fig pattern — a concept Claude already knows — and the generic 'Instructions' block ('Clarify goals...', 'Apply relevant best practices...', 'Provide actionable steps and verification') is pure filler.

2 / 5

Actionability

Each phase supplies a concrete subagent_type and a detailed, copy-paste-ready prompt with explicit expected outputs and context handoffs, giving fully executable guidance across the common migration cases.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with numbered steps, context handoffs, and validation safeguards (rollback triggers like 'error rate >1%', 24-hour observation windows, 30-day 0%-traffic verification before decommissioning); minor gaps in explicit 'validate before proceeding' checkpoints between phases keep it just below a 5.

4 / 5

Progressive Disclosure

The document is well-sectioned into phases, but it is a single monolithic SKILL.md with no bundle files and no one-level-deep references; detailed prompt templates that could live in separate files are all inlined.

3 / 5

Total

14

/

20

Passed

Description

53%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.

The description identifies a distinct niche and a couple of concrete actions but lacks an explicit 'Use when' trigger and is truncated mid-sentence in the frontmatter, leaving the 'what' itself incomplete. Keyword coverage is adequate but misses common synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when modernizing or migrating a legacy codebase, or when the user mentions strangler fig migration, legacy refactoring, or phased cutover').

Repair the truncated description so it does not end at 'through ex'; complete the sentence (e.g., '...through expert agent coordination').

Broaden trigger terms with synonyms users actually say — 'migration', 'refactoring', 'legacy code', 'phased cutover' — alongside 'strangler fig'.

DimensionReasoningScore

Specificity

Names the domain ('legacy system modernization') and the pattern ('strangler fig pattern') plus a couple of concrete actions ('gradual replacement of outdated components', 'maintaining continuous business operations'), but coverage is high-level rather than comprehensive.

3 / 5

Completeness

States a clear 'what' (orchestrate modernization via the strangler fig pattern) but provides no explicit 'when/Use when' trigger guidance, which per the guidelines caps completeness at 3; the description is also truncated mid-sentence at 'through ex'.

3 / 5

Trigger Term Quality

Includes the natural phrase 'legacy system modernization' but misses common synonyms users would say ('migration', 'refactoring', 'legacy code') and leans on the technical term 'strangler fig pattern'.

3 / 5

Distinctiveness Conflict Risk

The 'strangler fig pattern' framing carves out a clear niche that is unlikely to fire for unrelated skills, with only minor overlap risk against general refactoring or migration skills.

4 / 5

Total

13

/

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
rmyndharis/antigravity-skills
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.