CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

changelog

Old name of /write-changelog. Prints one line, then runs /write-changelog.

Quality

82%

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

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.

This is an exemplary minimal redirect skill: it explains just enough context, gives verbatim output, delegates cleanly with argument preservation, and guards against the model doing extra work. Nothing is missing and nothing is padded.

DimensionReasoningScore

Conciseness

Every line is operational: one sentence of context ("Several AI tools keep /changelog for a command of their own, so this skill is now /write-changelog"), the exact output line, the delegation step with its argument edge case, and a closing guard ("Do nothing else here"). No concepts Claude already knows are explained; nothing could be trimmed without losing clarity.

5 / 5

Actionability

The body is fully executable: the line to print is given verbatim with "Print this line exactly", the tool is named ("Run the write-changelog skill with the Skill tool"), and argument passing is specified including the empty case ("passing these arguments unchanged (none, if this is empty): $ARGUMENTS"). This is copy-paste-ready guidance covering the common cases.

5 / 5

Workflow Clarity

Two numbered steps in explicit sequence — print the redirect line first, then invoke the target skill — with the empty-arguments edge case handled and a terminal instruction ("Do nothing else here"). This is a simple single-purpose skill with an unambiguous action and no destructive or batch operations, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist, and none are mentioned), and the body is well organized with a header, brief context, and numbered steps — meeting the guideline for a 5 in this case.

5 / 5

Total

20

/

20

Passed

Description

58%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 concise, concrete, and accurately scoped to a redirect command, with a clear "what". Its main weakness is the absent explicit "when"/trigger clause and lack of natural synonyms beyond the literal command name, which caps completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user invokes /changelog or asks for the changelog command."

Include natural variations such as "change log" or "release notes" so the description surfaces when users phrase the request differently.

Briefly state what the printed line communicates (a deprecation/redirect notice) to sharpen the "what" without adding length.

DimensionReasoningScore

Specificity

"Prints one line, then runs /write-changelog" names two concrete actions that fully cover this redirect's behavior, with nothing vague. It sits between anchor 3 ("1-2 concrete actions, but not comprehensive" — here coverage is complete for a redirect) and below anchor 5 (which expects multiple actions), so 4 is the best fit.

4 / 5

Completeness

The "what" is clear ("Prints one line, then runs /write-changelog"), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the command name. Per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"changelog" is a specific, relevant keyword a user would naturally type, but the description misses common variations and synonyms such as "change log" or "release notes". This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than anchor 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

"Old name of /write-changelog" carves out a clear niche tied to one specific command, so it is mostly distinct with minimal conflict risk. It is not a 5 because it necessarily overlaps with the closely related /write-changelog skill on the "changelog" trigger term.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/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.