CtrlK
BlogDocsLog inGet started
Tessl Logo

changelog-gen

Rewrite every `docs/*/game/changelog/{order}.stable-{semver}.md` from a ref range. Default `--limit=20`.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/changelog-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 dense, actionable, well-organized changelog-generation playbook with strong conciseness and an explicit reviewer-gate validation loop appropriate to its batch PR-writing workflow; its only real gap is that the procedure is implied through bullets rather than an explicit numbered sequence.

DimensionReasoningScore

Conciseness

The body is a terse, imperative bullet list with no padding and no explanation of concepts Claude already knows; every line carries an actionable rule or command, so it earns the lean-and-efficient anchor.

5 / 5

Actionability

It provides concrete, executable guidance such as `rg -C2 -i '<term>' lang/po/{lang}.po | head`, `gh api`, the `<video controls src="URL" title="CAPTION"></video>` form, and a before/after table example, but several bullets are rule-based constraints (glossary traps, ordering rules) rather than copy-paste-ready commands, leaving minor gaps.

4 / 5

Workflow Clarity

A clear sequence is implied (parse refs, crawl/rank, write per-language docs, gate with reviewer, PR) and it includes an explicit validation feedback loop (MUST run reviewer, fix every valid issue, rerun or document why findings are not applied), which clears the batch-operation cap; it stops at 4 because the steps are implied via bullets rather than a numbered sequence with every checkpoint.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no bundle files to defer to; per the simple-skills scoring note it qualifies for the top anchor with well-organized sections (## Example command, ## Before/after example) and a single one-level external example reference.

5 / 5

Total

18

/

20

Passed

Description

53%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 specific and well-scoped to a distinct changelog-rewriting task, but it omits any "Use when..." trigger guidance and relies on path-pattern jargon rather than natural user language, capping completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when generating or refreshing per-language changelog files for a release."

Surface natural user-facing terms ("release notes", "changelog", "version bump") alongside the path pattern so users' phrasing matches the description.

Optionally enumerate the concrete actions (rewrite, localize, group PRs, gate with reviewer) to lift specificity from one verb to a fuller coverage list.

DimensionReasoningScore

Specificity

The description names a concrete action ("Rewrite every ... changelog ... from a ref range") and a specific path pattern, but enumerates only one action verb rather than multiple specific actions, so it sits at the domain-plus-1-2-actions anchor rather than the comprehensive level 4.

3 / 5

Completeness

It gives a clear "what" (rewrite changelog files from a ref range) but no "when" clause at all; per the judging guidelines a missing "Use when..." trigger caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant keywords like "changelog", "ref range", "stable", and "semver", but leans on technical path-pattern jargon and omits the natural phrases a user would say (e.g. "generate changelog", "release notes"), missing common variations.

3 / 5

Distinctiveness Conflict Risk

The bounded path pattern docs/*/game/changelog/{order}.stable-{semver}.md names a clear, niche task unlikely to collide with other skills, but the absence of an explicit trigger phrase keeps it below the minimal-conflict level 5.

4 / 5

Total

13

/

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
cataclysmbn/Cataclysm-BN
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.