api-versioning-strategy
Implements API versioning using URL paths, headers, or query parameters with backward compatibility and deprecation strategies. Use when managing multiple API versions, planning breaking changes, or designing migration paths.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill api-versioning-strategyOverall
score
89%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 a well-crafted skill description that excels across all dimensions. It provides specific implementation methods (URL paths, headers, query parameters), includes relevant technical terms developers would naturally use, and has an explicit 'Use when' clause with clear trigger scenarios. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implements API versioning using URL paths, headers, or query parameters' and includes 'backward compatibility and deprecation strategies' - these are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (implements API versioning with specific methods and strategies) AND when (explicit 'Use when' clause covering managing versions, planning breaking changes, designing migration paths). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'API versioning', 'URL paths', 'headers', 'query parameters', 'breaking changes', 'migration paths', 'multiple API versions' - good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API versioning with distinct triggers like 'API versions', 'breaking changes', 'migration paths' - unlikely to conflict with general API design or other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent conciseness and actionability. The code examples are executable and the tables efficiently convey comparison information. The main weaknesses are the lack of validation steps for implementing versioning changes and missing references to detailed migration guide resources.
Suggestions
Add a validation workflow for testing version compatibility before deploying new versions (e.g., contract testing, integration test steps)
Link to separate files for detailed migration guide templates and version-specific code examples rather than just mentioning them in best practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with well-organized tables, minimal prose, and code examples that demonstrate concepts without unnecessary explanation. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable JavaScript code for routing, version adapters, and deprecation headers. The comparison table and safe/breaking changes list give concrete, copy-paste ready guidance. | 3 / 3 |
Workflow Clarity | The deprecation timeline table provides a clear sequence, but lacks explicit validation checkpoints or feedback loops for the versioning implementation process itself. No guidance on testing version compatibility. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but everything is inline. Migration guides and code examples mentioned in best practices could be linked to separate files for complex implementations. | 2 / 3 |
Total | 10 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 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.