migration-guide-creator
Migration Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: migration guide creator, migration guide creator Part of the Technical Documentation skill category.
30
0%
Does it follow best practices?
Impact
81%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/migration-guide-creator/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 description is essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be indistinguishable from other documentation skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates step-by-step migration guides for API version upgrades, documents breaking changes, maps deprecated features to replacements, and creates compatibility matrices.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about upgrading, migrating between versions, handling breaking changes, deprecation notices, or creating upgrade/migration documentation.'
Remove the duplicate trigger term and expand with natural keyword variations users would actually say, such as 'upgrade guide', 'version migration', 'breaking changes', 'deprecation guide', 'migration steps', 'API upgrade'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('migration guide creator') but provides no concrete actions. It does not describe what the skill actually does—no mention of specific tasks like generating migration steps, comparing API versions, mapping deprecated features, etc. | 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 explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'migration guide creator' repeated twice. It lacks natural keywords users would say such as 'upgrade guide', 'migration steps', 'version upgrade', 'breaking changes', 'API migration', or 'deprecation'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Technical Documentation skill category' could overlap with any documentation skill. Without specific actions or distinct triggers, it would easily conflict with other documentation-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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 empty shell with no actual content. It consists entirely of generic boilerplate that describes what a migration guide creator skill would do without providing any actual guidance, examples, templates, or actionable instructions. It fails on every dimension because there is no substantive content to evaluate.
Suggestions
Add a concrete migration guide template with sections (e.g., prerequisites, breaking changes, step-by-step migration steps, rollback procedures, validation checklist) that Claude can use as a starting framework.
Include at least one complete worked example showing input (e.g., changelog or API diff) transformed into a migration guide output with specific formatting and structure.
Define a clear workflow: 1) Identify breaking changes, 2) Document prerequisites, 3) Write step-by-step migration instructions, 4) Add validation/verification steps, 5) Include rollback procedures.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with actionable content such as code examples for common migration patterns (database schema changes, API version upgrades, dependency updates).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'migration guide creator' excessively and explains nothing Claude doesn't already know. Every section is generic boilerplate with zero domain-specific content. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, templates, or any executable guidance whatsoever. The skill describes what it claims to do but never actually provides any instructions for creating migration guides. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed files, no examples section, and no layered content. The sections that exist contain no real information to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.