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

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/framework-migration-code-migrate/SKILL.md

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

Quality

Content

42%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 well-organized into clear sections and outlines a sensible migration deliverable sequence, but its instructions are vague and abstract, contain no executable guidance, and rely on a referenced playbook file that is missing from the bundle.

Suggestions

Replace the abstract Instruction bullets with concrete, executable steps (specific commands, tool invocations, or migration techniques) or ensure the referenced playbook file actually exists.

Add explicit validation checkpoints and a fix->retry feedback loop in the migration workflow to satisfy the destructive-operation requirement and lift workflow clarity above 3.

Remove the redundant restated description and circular trigger clauses to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain basic concepts, but it carries redundancy: the opening line restates the description verbatim, the 'Use this skill when' bullets are circular ('Working on code migration assistant tasks'), and the closing line repeats points already made.	3 / 5
Actionability	Guidance is abstract ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no executable code or specific commands, and the concrete examples are deferred to resources/implementation-playbook.md which is not present in the bundle.	2 / 5
Workflow Clarity	The Output Format lists a coherent ordered migration sequence (analysis -> risk -> plan -> code -> testing -> rollback -> tracking -> docs) and names testing/rollback, but validation appears only abstractly with no explicit checkpoints or fix->retry feedback loops; since migration is a risky/destructive operation the cap of 3 applies.	3 / 5
Progressive Disclosure	Section structure is clean and the reference to the playbook is clearly signaled at one level, but the referenced file resources/implementation-playbook.md does not exist in the bundle, so the detailed patterns/examples the overview points to are not actually available.	3 / 5
	Total	11 / 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 clearly identifies the code-migration domain and a couple of concrete deliverables, but it is truncated mid-sentence, uses second-person voice, and lacks any 'Use when...' trigger guidance, leaving completeness and specificity below their potential.

Suggestions

Complete the truncated sentence and convert to third-person voice (e.g., 'Generates comprehensive migration plans, automated migration scripts, and rollback strategies').

Add an explicit 'Use when...' trigger clause with natural user phrases (migrate, port, upgrade, refactor) to lift completeness past 3.

Include common synonyms and file/extension cues users would actually say to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('transitioning codebases between frameworks, languages, versions, and platforms') and 1-2 concrete actions ('Generate comprehensive migration plans, automated migration scripts'), but the sentence is truncated mid-list so coverage is incomplete; the second-person phrasing 'You are a code migration expert' incurs the -1 specificity penalty per the guidelines.	2 / 5
Completeness	It clearly states what the skill does (migration plans and scripts across stacks) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the guidelines; it is not a 2 because the 'what' is concrete rather than vague.	3 / 5
Trigger Term Quality	Relevant keywords appear ('code migration', 'frameworks', 'languages', 'versions', 'platforms', 'migration plans', 'migration scripts'), but common natural synonyms users would say such as 'port', 'upgrade', or 'refactor' are missing and the truncation limits full coverage.	3 / 5
Distinctiveness Conflict Risk	'Code migration' is a recognizable niche but the scope ('frameworks, languages, versions, and platforms') is broad enough to overlap with refactoring, version-upgrade, or framework-specific skills, fitting the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/framework-migration-code-migrate/SKILL.md
Commit: 57c135b

Reviewed: 4 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.