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 stub or placeholder than a functional description. 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, including rollback strategies and data transformation scripts.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about migrating databases, upgrading schemas, planning data moves, or creating migration roadmaps.'

Specify the domain of migration (database, cloud, platform, code, etc.) to make the skill clearly distinguishable from other potential migration-related skills.

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 data', etc.	1 / 3
Distinctiveness Conflict Risk	'Migration-plan' is extremely generic—it could refer to database migration, cloud migration, code migration, data migration, platform migration, or any number of other domains. 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 migration reference document that repeats the same YAML agent definition pattern 20+ times inline, consuming massive token budget without proportional value. The actual actionable migration workflow is buried at the bottom in 5 vague steps with no validation or error recovery. The content would be far more effective as a concise template + mapping table with agent definitions split into separate files.

Suggestions

Replace the 20+ inline YAML blocks with a single template example and a summary table mapping command paths to agent names/roles/key tools, moving full definitions to separate files

Expand the 'Migration Steps' section with executable commands (e.g., mkdir commands, file creation scripts) and add explicit validation checkpoints after each step

Add a concrete verification workflow: how to test that a migrated agent works correctly, with specific commands to run and expected outputs to check

Remove explanatory text about what agents, tool restrictions, and inter-agent communication are — focus only on the specific migration procedure and format requirements

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines, mostly repetitive YAML blocks that follow the same pattern. The document explains obvious concepts (what agents do, what tool restrictions mean) and could be reduced to a template + table mapping commands to agents. Most content is redundant boilerplate.	1 / 3
Actionability	The YAML agent definitions are concrete and specific, providing exact tool names, trigger patterns, and role definitions. However, the actual migration steps (section 4) are vague ('Create directory structure', 'Test agent interactions') with no executable commands 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, and no verification that migration succeeded. For a destructive operation like system migration, this completely lacks the feedback loops and validation steps needed. The monitoring section lists metrics but provides no concrete way to measure them.	1 / 3
Progressive Disclosure	This is a monolithic wall of text with 20+ nearly identical YAML blocks inlined. The agent definitions should be in separate files or a reference document, with the SKILL.md providing just the template format, migration workflow, and a summary table mapping commands to agents.	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: f547cec

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.