agent-migration-plan

Agent skill for migration-plan - invoke with $agent-migration-plan

1.83x

Quality

Does it follow best practices?

Impact

99%

1.83x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-migration-plan/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an extremely weak description that provides virtually no useful information for skill selection. It reads more like a label or invocation instruction than a description of capabilities. It fails on every dimension: no concrete actions, no natural trigger terms, no 'what/when' guidance, and no distinctiveness.

Suggestions

Describe specific concrete actions the skill performs, e.g., 'Generates step-by-step migration plans for database schema changes, framework upgrades, or cloud infrastructure transitions.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about migrating databases, upgrading frameworks, planning a cloud migration, or creating a migration roadmap.'

Specify the domain or type of migration to distinguish this skill from other potentially similar skills, e.g., clarify whether this is for code migrations, infrastructure migrations, data migrations, etc.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for migration-plan' is entirely vague—it doesn't describe what the skill actually does, what kind of migration, or any specific capabilities.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	The only potentially relevant keyword is 'migration-plan', which is a hyphenated technical term rather than natural language a user would say. There are no natural trigger terms like 'migrate', 'database migration', 'upgrade', 'move to new version', etc.	1 / 3
Distinctiveness Conflict Risk	'Migration-plan' is extremely generic—it could refer to database migrations, cloud migrations, framework migrations, data migrations, or any number of other contexts. There is nothing to distinguish this skill from other migration-related skills.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is an extremely verbose catalog of agent YAML definitions that repeats the same structural pattern 20+ times without providing actionable migration guidance. The actual migration workflow—the ostensible purpose of the skill—is relegated to a vague 5-step list with no validation, no executable commands, and no error handling. The content would be far more effective as a concise template with a mapping table and actual migration scripts.

Suggestions

Replace the 20+ inline YAML blocks with a single template example and a concise table mapping command names to agent roles, tools, and triggers—link to individual agent definition files if needed.

Add concrete, executable migration commands (e.g., mkdir commands, file copy/rename scripts, validation commands) to the Migration Steps section instead of abstract descriptions.

Add explicit validation checkpoints to the migration workflow: how to verify each agent activates correctly, how to test backwards compatibility, and how to rollback if something fails.

Split agent definitions into separate files (one per agent or per category) and reference them from a concise overview table in the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines, mostly consisting of repetitive YAML blocks that follow the same pattern. The document explains obvious concepts (what agents do, what tools are) and could be condensed to a fraction of its size with a template + table mapping commands to agents. Massive token waste with no proportional information gain.	1 / 3
Actionability	The YAML agent definitions are concrete and structured, providing specific tool names, trigger patterns, and role assignments. However, the actual migration steps (section 4) are vague ('Create directory structure', 'Convert each command') with no executable commands, scripts, or concrete examples of how to perform the migration itself.	2 / 3
Workflow Clarity	The migration steps in section 4 are a brief 5-item list with no validation checkpoints, no error recovery, no feedback loops, and no verification that migration succeeded. For a destructive system transformation, this is critically insufficient. The 'Monitoring Migration Success' section lists metrics but provides no concrete way to measure them.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All 20+ agent definitions are inlined when they should each be separate files or at minimum summarized in a table with links. No bundle files exist to support progressive disclosure, and the content makes no attempt to organize into layers.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (751 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ruvnet/claude-flow
Commit: 9d4a9ea

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