CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

changelog

Creates and maintains CHANGELOG.md in Keep a Changelog format, including adding entries and cutting releases. Use when the user asks to update the changelog, add a changelog entry, or record a release.

1.05x
Quality

95%

Does it follow best practices?

Impact

100%

1.05x

2 of 3 eval scenarios. Add 1 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

The body is a lean, fully actionable instruction set: concrete skeletons, exact commands, and validation checkpoints before every write. Structure is appropriately self-contained for a skill of this size with no missing bundle references.

DimensionReasoningScore

Conciseness

Every line is a rule, a step, or a template — e.g. "If it exists, stop and report it — do not overwrite" and "Get today's date with `date +%F`. Do not guess it." — with no explanation of concepts Claude already knows and nothing to trim.

5 / 5

Actionability

Provides a complete skeleton, exact commands (`date +%F`), exact heading formats (`## [X.Y.Z] - YYYY-MM-DD`), and numbered steps for all three operations — fully executable guidance.

5 / 5

Workflow Clarity

Each operation is clearly sequenced with explicit validation: a pre-flight checklist for --release ("Check before writing, and stop with the reason if any fails"), an existence check for --create, and type rejection for --add-entry.

5 / 5

Progressive Disclosure

A single-purpose, well-organized skill (Usage / Skeleton / three Operations / Entry Style) where all content belongs in SKILL.md; no external references are needed or dangling, so the simple-skill exception applies.

5 / 5

Total

20

/

20

Passed

Description

92%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.

The description is a strong example: third-person voice, concrete actions matching the skill's three operations, and an explicit trigger clause with natural user phrasing. The only gap is a few missing synonyms (e.g., "release notes") that slightly limit trigger recall.

DimensionReasoningScore

Specificity

Names the artifact (CHANGELOG.md), the format (Keep a Changelog), and three concrete actions — creating, adding entries, and cutting releases — which comprehensively covers the skill's operation set.

5 / 5

Completeness

Explicitly answers "what" (creates and maintains CHANGELOG.md in Keep a Changelog format, adds entries, cuts releases) and "when" via a concrete "Use when the user asks…" clause with three trigger phrases.

5 / 5

Trigger Term Quality

"update the changelog", "add a changelog entry", and "record a release" are natural user phrases, but synonyms such as "release notes" or "cut a release" are missing.

4 / 5

Distinctiveness Conflict Risk

"changelog" is a clear niche with distinct triggers; only minimal overlap risk with generic git or release-versioning skills.

5 / 5

Total

19

/

20

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

rikdc/ai-skills

Path

plugins/git-workflow/skills/changelog/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.