agent-migration-plan
Agent skill for migration-plan - invoke with $agent-migration-plan
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-migration-plan39
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 99%
↑ 1.83xAgent success when using this skill
Validation for skill structure
Discovery
0%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 description is critically underdeveloped, functioning only as a label rather than a useful skill description. It fails to explain what type of migrations it handles, what actions it performs, or when Claude should select it. The invocation syntax is the only concrete information provided, which is insufficient for skill selection among multiple options.
Suggestions
Specify the type of migration this skill handles (e.g., database schema migrations, cloud platform migrations, framework version upgrades) and list 2-3 concrete actions it performs.
Add a 'Use when...' clause with natural trigger terms users would say, such as 'migrate', 'upgrade', 'convert', 'move to', or specific technology names relevant to the migration type.
Include file types, frameworks, or technologies this skill works with to create a distinct niche and prevent conflicts with other potential migration-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only states it's an 'Agent skill for migration-plan' without explaining what migrations it handles, what actions it performs, or what outputs it produces. | 1 / 3 |
Completeness | Missing both 'what' and 'when' - doesn't explain what the skill does beyond its name, and provides no guidance on when Claude should select it. Only describes how to invoke it. | 1 / 3 |
Trigger Term Quality | The only keyword is 'migration-plan' which is technical jargon. Missing natural terms users would say like 'migrate', 'database migration', 'code migration', 'upgrade', 'convert', or specific technology names. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'migration' could apply to database migrations, code migrations, cloud migrations, data migrations, or version upgrades. No specificity to distinguish from other potential 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 a comprehensive but poorly structured migration reference document. While it provides concrete agent YAML definitions, it suffers from extreme verbosity, lack of executable migration procedures, and poor organization. The content would be far more useful as a concise overview with agent definitions split into separate files and actual migration scripts provided.
Suggestions
Extract individual agent definitions into separate files (e.g., `agents/swarm-initializer.md`) and replace inline definitions with a summary table linking to each file
Add concrete, executable migration commands: `mkdir -p .claude/agents && cp templates/*.yaml .claude/agents/`
Include validation checkpoints in the migration workflow: 'Run `./scripts/validate-agents.sh` to verify all agents load correctly before proceeding'
Condense the repeated YAML structure into one annotated example, then use a table to show agent-specific values (name, role, tools, triggers)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 600+ lines with extensive repetition. Each agent definition follows the same template pattern that could be condensed into a single example plus a table. The document explains obvious concepts and includes unnecessary boilerplate throughout. | 1 / 3 |
Actionability | Provides concrete YAML agent definitions that are copy-paste ready, but lacks executable migration scripts or commands. The 'Migration Steps' section is vague ('Create directory structure', 'Test agent interactions') without specific commands or validation procedures. | 2 / 3 |
Workflow Clarity | The 5-step migration process is extremely high-level with no validation checkpoints, no error recovery procedures, and no concrete verification steps. For a migration involving system transformation, this lacks the necessary rigor to prevent failures. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All 15+ agent definitions are inline when they should be in separate files with a summary table in the main document. No navigation structure or clear organization for discovery. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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 | |
- 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.