agent-migration-plan
Agent skill for migration-plan - invoke with $agent-migration-plan
39
7%
Does it follow best practices?
Impact
99%
1.83xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-migration-plan/SKILL.mdQuality
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 is an extremely weak description that provides virtually no useful information for skill selection. It reads like an auto-generated stub rather than a crafted description, containing no concrete actions, no trigger terms, no 'when to use' guidance, and no domain specificity. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Specify what kind of migration this skill handles (e.g., database migration, cloud migration, framework upgrade) and list concrete actions like 'generates step-by-step migration plans, identifies breaking changes, creates rollback strategies'.
Add an explicit 'Use when...' clause with natural trigger terms users would say, such as 'Use when the user needs to plan a migration, upgrade a system, move between versions, or create a migration roadmap'.
Remove the invocation syntax ('invoke with $agent-migration-plan') from the description—this is implementation detail, not selection-relevant information—and replace it with domain-specific context that distinguishes this skill from other tools.
| 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 exhaustive catalog of agent YAML definitions that suffers from extreme repetition and poor organization. While the individual agent definitions are concrete, the actual migration workflow—the core purpose of the skill—is underdeveloped with no validation steps, no executable commands, and no error recovery. The content would be far more effective as a concise migration guide with one template example and a reference file containing the full agent catalog.
Suggestions
Extract all agent YAML definitions into a separate reference file (e.g., AGENT-CATALOG.md) and keep only one example template in the main skill body with a link to the full catalog.
Expand the 'Migration Steps' section with executable commands (e.g., mkdir, cp/mv commands, validation scripts) and explicit verification checkpoints after each step.
Add a rollback procedure with concrete steps for reverting if migration fails, since this is a destructive batch operation.
Replace the repetitive full YAML blocks with a summary table (command → agent name → role → key tools) and a single detailed template example that demonstrates the pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 500+ lines, mostly consisting of repetitive YAML blocks that follow identical patterns. The same structure (role, responsibilities, capabilities, tools, triggers) is repeated 15+ times with minor variations. This could be condensed to a template + table mapping commands to agents. Claude doesn't need every agent definition spelled out in full when the pattern is clear after one example. | 1 / 3 |
Actionability | The YAML agent definitions are concrete and specific, with clear tool restrictions and trigger patterns. However, the actual migration steps (section 4) are vague ('Create directory structure', 'Convert each command') without executable commands or scripts. The skill is more of a reference catalog than actionable migration guidance. | 2 / 3 |
Workflow Clarity | The migration steps in section 4 are a brief 5-item list with no validation checkpoints, no error recovery, no verification that migration succeeded, and no rollback procedures despite this being a destructive/batch operation (converting an entire command system). The 'Monitoring Migration Success' section lists metrics but provides no way to actually measure them. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with 15+ nearly identical YAML blocks inline. The agent definitions should be in separate files or a reference document, with the SKILL.md providing just the migration workflow, a template, and links to the full catalog. No external references are used despite the content clearly warranting them. | 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 | |
- Repository
- ruvnet/ruflo
- Commit
3d8f171
- 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.