migrating-apis
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill migrating-apisImplement API migrations between versions, platforms, or frameworks with minimal downtime. Use when upgrading APIs between versions. Trigger with phrases like "migrate the API", "upgrade API version", or "migrate to new API".
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
22%This skill content is severely lacking in actionable guidance for API migration. It reads as a generic template with placeholder text rather than a practical migration guide. The absence of concrete migration patterns, version compatibility handling, rollback strategies, and executable code makes it nearly unusable for its stated purpose.
Suggestions
Add concrete code examples showing actual API migration patterns (e.g., endpoint versioning, request/response transformation, deprecation handling)
Fix the duplicate step numbering and add explicit validation checkpoints with rollback procedures for failed migrations
Remove the duplicate overview sentence and generic prerequisites; replace with migration-specific requirements like 'source API version' and 'target API version'
Include at least one complete migration example inline showing before/after code and the transformation process
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary filler phrases like 'This skill provides automated assistance for api migration tool tasks' repeated twice, and generic prerequisites that Claude would know. However, the structure is reasonably compact overall. | 2 / 3 |
Actionability | Extremely vague with no concrete code examples, specific commands, or executable guidance. Instructions like 'Generate boilerplate code using Bash(api:migrate-*)' lack actual implementation details. No migration-specific patterns, version handling, or actual migration code provided. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbering (two separate lists both starting at 1), no validation checkpoints for migration operations, and no rollback or verification steps for what should be a critical multi-step process with potential for data loss. | 1 / 3 |
Progressive Disclosure | References external files appropriately (implementation.md, errors.md, examples.md), but the main content is too thin to serve as a useful overview. The skill offloads almost all substance to external files without providing enough actionable content in the main document. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
82%This is a solid description with explicit trigger guidance and clear 'Use when' clause. The main weakness is the lack of specific concrete actions - it describes the general capability but not the specific tasks it performs. The trigger terms are natural and well-chosen.
Suggestions
Add specific concrete actions like 'update endpoint signatures', 'transform request/response schemas', 'generate compatibility layers', or 'handle breaking changes'
Narrow the scope or add more distinctive terms to reduce potential overlap with general API or refactoring skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (API migrations) and mentions some context (versions, platforms, frameworks, minimal downtime), but doesn't list specific concrete actions like 'update endpoints', 'transform request/response schemas', or 'handle deprecation warnings'. | 2 / 3 |
Completeness | Clearly answers both what (implement API migrations between versions/platforms/frameworks with minimal downtime) and when (explicit 'Use when' clause and 'Trigger with phrases' providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Includes good natural trigger phrases users would say: 'migrate the API', 'upgrade API version', 'migrate to new API'. Also covers variations like 'versions', 'platforms', 'frameworks'. | 3 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to API migrations, but could potentially overlap with general 'API development' or 'code refactoring' skills. The term 'frameworks' is broad and might cause conflicts with framework-specific skills. | 2 / 3 |
Total | 10 / 12 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.