migration-guide-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill migration-guide-creatorMigration Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: migration guide creator, migration guide creator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with minimal useful content. It relies entirely on the skill name for context and provides no concrete actions, natural trigger terms, or explicit usage guidance. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific concrete actions like 'Creates step-by-step migration guides for API version upgrades, documents breaking changes, generates compatibility matrices, and provides code migration examples'.
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions migration guide, upgrade documentation, version migration, breaking changes, API upgrade, or needs help documenting how to migrate between versions'.
Remove the redundant duplicate trigger term and expand with variations users would naturally say like 'upgrade guide', 'migration docs', 'version upgrade instructions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Migration Guide Creator' and category 'Technical Documentation'. There are no specific capabilities listed like 'creates step-by-step migration instructions' or 'documents breaking changes'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'migration guide creator' repeated twice, which is the skill name itself. Missing natural user phrases like 'upgrade guide', 'version migration', 'breaking changes', 'upgrade path', or 'migration documentation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'migration guide' is somewhat specific to a documentation niche, but 'Technical Documentation' is broad and could overlap with many other documentation skills. Without specific triggers, it could conflict with general documentation or upgrade-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about migration guide creation. It consists entirely of generic boilerplate that could apply to any skill topic, providing zero actionable guidance, examples, or workflows for creating migration documentation.
Suggestions
Add a concrete migration guide template or structure (e.g., sections for prerequisites, breaking changes, step-by-step migration steps, rollback procedures)
Include at least one executable example showing how to document a specific type of migration (API version upgrade, database schema change, etc.)
Define a clear workflow with validation checkpoints: identify breaking changes → document prerequisites → write migration steps → add verification tests → review checklist
Replace generic capability claims with specific techniques like 'Use semantic versioning headers' or 'Include before/after code comparisons for API changes'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about migration guide creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | No concrete guidance, code, commands, or examples are provided. The skill describes what it claims to do but never actually instructs how to create a migration guide. 'Provides step-by-step guidance' is stated but no steps are given. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, sequences, or validation checkpoints for creating migration guides. The content is entirely meta-description without any actual process. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, examples, or templates. The content is a shallow placeholder with no depth or navigation to additional resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.