api-changelog-versioning
Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions, communicating breaking changes, or creating upgrade guides.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill api-changelog-versioningOverall
score
89%
Validation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
87%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 that provides concrete, actionable templates for API changelog documentation. The content is appropriately concise and includes useful before/after examples. The main weakness is the migration workflow lacks explicit validation steps or error recovery guidance for what is potentially a risky operation.
Suggestions
Add validation checkpoints to the migration guide template (e.g., 'Test endpoint responses match expected v3 format before proceeding')
Include a rollback procedure or verification step after each migration phase to catch issues early
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section provides direct, actionable templates without explaining what APIs or changelogs are. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready templates including markdown structure, JSON examples, and migration steps. The before/after code examples are immediately usable. | 3 / 3 |
Workflow Clarity | Migration steps are listed but lack validation checkpoints. No guidance on verifying migration success or rollback procedures if something fails during the upgrade process. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), content is well-organized into logical sections (structure, deprecation, policy, migration, best practices) without needing external file references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 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 |
Total | 14 / 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.