CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

83%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A token-efficient, highly actionable template/reference skill with concrete copy-paste examples. Weaker on workflow clarity because it presents output structure rather than an explicit Claude-facing process with validation checkpoints.

Suggestions

Add a short numbered "How to produce a changelog" workflow for Claude (gather changes → classify breaking/deprecated/feature → fill template → verify migration steps), with an explicit verify/review checkpoint before publishing.

Collapse the Deprecation Schedule table and Version Support Policy list into one section to remove the overlap between current/maintenance/EOL status and its description.

Add one explicit validation step in the migration guide template (e.g. "Confirm staging tests pass before updating production") so the checkpoint is signaled rather than implied.

DimensionReasoningScore

Conciseness

The body is lean templates and tables with no re-explanation of what APIs or changelogs are; every section (changelog structure, deprecation schedule, support policy, migration template, best practices) earns its place.

5 / 5

Actionability

Copy-paste ready markdown and JSON templates with concrete before/after examples (e.g. `{ "user_name": "john" }` → `{ "data": { "type": "user", ... } }`) directly cover the common changelog and migration cases.

5 / 5

Workflow Clarity

Content is organized as output templates rather than a Claude-facing process; the only sequencing/checkpoint ("Test in staging environment") lives inside an end-user migration example, so the skill-level workflow and validation are implicit rather than explicit.

3 / 5

Progressive Disclosure

Self-contained with well-labeled sections and no nested references, but at ~75 lines with slight redundancy between the Deprecation Schedule table and Version Support Policy list it is just over the simple-skill threshold.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, well-structured description that answers both what and when with concrete, natural trigger phrases and a distinct niche. Slightly conservative on specificity because the action set radiates from one core verb.

DimensionReasoningScore

Specificity

"Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies" enumerates several specific documentation actions, though they all branch from the single primary verb "Creates" rather than being distinct operations.

4 / 5

Completeness

It explicitly states what ("Creates comprehensive API changelogs...") and when ("Use when managing API versions, communicating breaking changes, or creating upgrade guides") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"managing API versions, communicating breaking changes, or creating upgrade guides" are natural phrases a user would say, but a few common synonyms (e.g. release notes, version bumps) are missing.

4 / 5

Distinctiveness Conflict Risk

The API changelog/versioning niche is clearly scoped with triggers specific enough to avoid overlapping with generic documentation or release skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.