CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

72

Quality

90%

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

93%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 lean, highly actionable skill built almost entirely from concrete, copy-paste-ready templates with no padding. The only gap is the absence of an explicit validation step for the changelog-authoring workflow itself.

DimensionReasoningScore

Conciseness

The body is pure templates, tables, and best-practice bullets with zero explanation of concepts Claude already knows; dates appear only inside illustrative example templates, and every token earns its place.

5 / 5

Actionability

Provides copy-paste-ready changelog and migration-guide templates with realistic entries, before/after JSON examples, and a concrete deprecation schedule table, covering the common cases for this task.

5 / 5

Workflow Clarity

The migration template sequences concrete steps including a 'Test in staging environment' checkpoint, but there is no validation or feedback loop for Claude's own changelog-authoring process (e.g., verifying every breaking change has a migration step).

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the ~75-line body is compact, clearly sectioned, fully self-contained, and easy to navigate, matching the simple-skill exception for well-organized single-file skills.

5 / 5

Total

19

/

20

Passed

Description

83%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 strong description with explicit what and when clauses and natural trigger phrases. Its only weaknesses are the buzzword 'comprehensive' and a trigger list missing common synonyms like 'changelog' and 'release notes'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('documenting breaking changes, deprecations, and migration strategies') but 'comprehensive' is mild buzzword padding and the actions cluster around one operation rather than a full breadth of capabilities, so it falls just below the comprehensive-coverage anchor.

4 / 5

Completeness

Explicitly answers both what ('Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies') and when ('Use when managing API versions, communicating breaking changes, or creating upgrade guides') with three concrete trigger phrases.

5 / 5

Trigger Term Quality

'managing API versions, communicating breaking changes, creating upgrade guides' are natural user phrases, but common synonyms like 'changelog', 'release notes', or 'versioning' are absent from the trigger list.

4 / 5

Distinctiveness Conflict Risk

Clear niche (API changelogs and version migration) with distinct triggers, though minor overlap risk exists with general documentation or git-changelog skills.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/api-changelog-versioning/skills/api-changelog-versioning/SKILL.md

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.