CtrlK
BlogDocsLog inGet started
Tessl Logo

framework-migration-code-migrate

You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and

37

Quality

35%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/framework-migration-code-migrate/SKILL.md

The canonical home for this skill is framework-migration-code-migrate in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

25%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 short and sectioned but almost entirely generic boilerplate with no executable guidance, no validation checkpoints for risky migration work, and a dangling reference to a non-existent playbook file.

Suggestions

Replace the abstract Instructions with concrete, executable steps (e.g. specific diff/transform commands, a code-transformation script skeleton, and a comparison-test command).

Add explicit validation checkpoints in the workflow (e.g. run the test suite, diff old vs new behavior, and only proceed when green), since migration is destructive and currently lacks any verification loop.

Either create 'resources/implementation-playbook.md' with real patterns/examples or remove the broken reference; ensure referenced bundle paths actually exist.

DimensionReasoningScore

Conciseness

The body is lean and does not over-explain concepts Claude already knows, but it includes low-value boilerplate (circular 'Use this skill when...code migration assistant tasks' and a redundant 'Do not use this skill when' section) that could be trimmed.

3 / 5

Actionability

Instructions are entirely abstract ('Clarify goals... Apply relevant best practices... Provide actionable steps and verification') with no concrete code, commands, or examples; the Output Format only names deliverables without showing how to produce them.

1 / 5

Workflow Clarity

A rough structure exists (Instructions bullets + Output Format list), but steps are generic and undefined, and there are no validation checkpoints. Since code migration is destructive/risky, missing validation caps this dimension; anchor 2 fits because validation is absent and steps are poorly defined.

2 / 5

Progressive Disclosure

Sections are present, but the only reference ('resources/implementation-playbook.md') points to a file that does not exist in the bundle (no references/ or resources/ directory is present), so navigation leads nowhere.

2 / 5

Total

8

/

20

Passed

Description

45%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 real niche and several actions, but it is truncated mid-sentence, written in second person, and lacks any explicit 'Use when' trigger guidance, capping its completeness and specificity.

Suggestions

Complete the truncated sentence and rewrite in third person (e.g. 'Generates comprehensive migration plans, automated migration scripts, and rollback strategies for transitions across frameworks, languages, versions, and platforms').

Add an explicit trigger clause: 'Use when the user asks to migrate, port, or upgrade a codebase across frameworks, languages, versions, or platforms.'

Add natural synonyms users say ('upgrade', 'port', 'refactor for', 'migrate from X to Y') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('transitioning codebases between frameworks, languages, versions, and platforms') and two actions ('Generate comprehensive migration plans, automated migration scripts'), but the sentence is truncated mid-clause ('...scripts, and'). The description uses second person ('You are a code migration expert'), which per the rubric reduces the specificity score by one from a base of 3.

2 / 5

Completeness

It clearly states what the skill does (migration expert generating plans and scripts) but provides no 'Use when...' trigger clause; the rubric caps completeness at 3 when explicit trigger guidance is missing. The truncated sentence further weakens the 'what'.

3 / 5

Trigger Term Quality

'code migration', 'frameworks', 'languages', 'versions', and 'platforms' are relevant keywords a user might say, but common variations/synonyms and concrete trigger phrases (e.g. 'upgrade', 'port', 'migrate from X to Y') are missing.

3 / 5

Distinctiveness Conflict Risk

'Code migration' is a recognizable niche, but spanning frameworks, languages, versions, AND platforms is very broad and could overlap with version-upgrade, refactoring, or language-porting skills.

3 / 5

Total

11

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.