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 essentially only provides a name and invocation command. It fails on every dimension: no concrete actions, no natural trigger terms, no explanation of what it does or when to use it, and no distinguishing characteristics. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.

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 transitions, or creating migration roadmaps.'

Specify the type of migration (database, cloud, framework, etc.) to make the skill clearly distinguishable from other potentially similar skills.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for migration-plan' is entirely vague—it doesn't describe what the skill 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 term is 'migration-plan', which is hyphenated and technical. There are no natural keywords a user would say, such as 'migrate', 'database migration', 'upgrade', 'transition', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that 'migration' could refer to database migration, cloud migration, code migration, data migration, or any other type. It provides no distinguishing details to differentiate it from other 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, repetitive document that lists 15+ agent YAML definitions inline with minimal variation between them. It lacks actionable migration instructions, has no validation or verification steps for what is fundamentally a system transformation task, and fails to leverage progressive disclosure by inlining everything into a single massive file. The content would be far more effective as a concise template + mapping table with individual agent definitions in separate files.

Suggestions

Replace the 15+ inline YAML blocks with a single agent definition template and a concise table mapping each command to its agent name, role, key tools, and trigger pattern — move full definitions to individual files under an agents/ directory.

Add concrete, executable migration steps with actual shell commands (e.g., `mkdir -p .claude/agents/coordination`, `cp .claude/commands/coordination/init.md .claude/agents/coordination/swarm-initializer.md`) and explicit validation checkpoints after each phase.

Add a verification workflow: after migration, run a validation script or checklist that confirms all commands have equivalent agents, tests trigger pattern matching, and verifies no functionality was lost.

Remove explanatory sections like 'Agent Activation' and 'Inter-Agent Communication' that describe concepts Claude already understands, and replace with only the project-specific conventions that differ from defaults.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 500+ lines, mostly consisting of repetitive YAML blocks that follow the same pattern. The document explains concepts Claude already understands (what agents are, what tool restrictions mean) and repeats nearly identical structures 15+ times. The entire content could be condensed to a template + table mapping commands to agents.	1 / 3
Actionability	The YAML agent definitions are concrete and structured, providing specific tool names, trigger patterns, and role assignments. However, the migration steps at the end are vague ('Create directory structure', 'Convert each command') with no executable commands, scripts, or concrete examples of how to actually perform the migration.	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 concrete commands. For a destructive migration operation (converting an entire command system), the lack of validation steps, rollback procedures, and verification is a critical gap.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All 15+ agent definitions are inlined when they should each be in 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: 2b9e2de

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