versioning-apis
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill versioning-apisImplement API versioning with backward compatibility, deprecation notices, and migration paths. Use when managing API versions and backward compatibility. Trigger with phrases like "version the API", "manage API versions", or "handle API versioning".
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
7%This skill fails to address its stated purpose of API versioning with backward compatibility, deprecation notices, and migration paths. Instead, it provides generic API development boilerplate with no versioning-specific guidance, code examples, or concrete strategies. The content would be equally (un)helpful for any API task.
Suggestions
Add concrete code examples showing versioning strategies: URL path versioning (/v1/users), header versioning (Accept: application/vnd.api+json;version=1), and query param versioning
Include specific deprecation notice patterns with example response headers (Deprecation, Sunset) and response body warnings
Provide a migration workflow with validation steps: test backward compatibility, verify deprecated endpoints still work, validate new version responses
Remove generic API development content and focus specifically on versioning concerns: version negotiation, maintaining multiple versions, sunset policies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't teach API versioning specifically. Phrases like 'automated assistance for api versioning manager tasks' and generic prerequisites (testing tools, auth strategies) waste tokens on things Claude already knows. | 1 / 3 |
Actionability | No concrete code examples for versioning strategies (URL path, header, query param). Instructions are vague ('Define resource models', 'Plan error handling') with no executable commands or specific versioning patterns. The Bash command 'api:version-*' is undefined. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbering (two separate lists starting at 1). No validation checkpoints for versioning migrations, no feedback loops for backward compatibility testing, and critical versioning workflow (deprecation notices, migration paths) is completely absent. | 1 / 3 |
Progressive Disclosure | References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is generic and doesn't provide a useful overview of API versioning. The skill offloads too much to external files without establishing core concepts. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (versioning, backward compatibility, deprecation notices, migration paths), includes explicit 'Use when' guidance, and offers natural trigger phrases. The description is concise yet comprehensive, clearly distinguishing this skill from other API-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implement API versioning', 'backward compatibility', 'deprecation notices', and 'migration paths' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (implement versioning with backward compatibility, deprecation notices, migration paths) AND when (explicit 'Use when' clause plus 'Trigger with phrases' section). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'version the API', 'manage API versions', 'handle API versioning', plus keywords like 'backward compatibility' and 'API versions'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API versioning - distinct from general API design, documentation, or other API-related skills. The specific triggers around 'versioning' and 'backward compatibility' reduce conflict risk. | 3 / 3 |
Total | 12 / 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.