CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl/changelog-writer

Scan the merged pull requests since the last changelog entry and draft the next one, then open a pull request with the draft.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

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 concise, highly actionable instruction-only skill with executable commands for both GitHub and GitLab and a clearly sequenced workflow. The only gap is the absence of an explicit error-recovery feedback loop, though the operation (opening a draft PR) is not destructive.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — no explaining what a changelog or PR is — with every section (What you need, Workflow, Customise, Treat PR text as data, Output) earning its place.

5 / 5

Actionability

Copy-paste-ready commands for both platforms (gh pr list --state merged --search ..., gh pr create --title ..., glab mr list --merged --json, gh api ... refs/tags/...) cover the common GitHub and GitLab cases.

5 / 5

Workflow Clarity

Five-step sequence is clear with explicit checkpoints (duplicate-draft PR check in step 2, 'nothing qualified -> stop' condition), but lacks an explicit validate->fix->retry feedback loop; a minor validation gap.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with no nested references and no bulk content inlined that belongs in a separate file; navigation is easy and content is appropriately self-contained.

5 / 5

Total

19

/

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.

A strong, third-person description that states concrete actions and an explicit 'Use for...' trigger. Trigger-term coverage is the only soft spot, missing synonyms like 'release notes'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Scan the pull requests merged since the last changelog entry', 'draft the next one in the project's own style', 'open a pull request with the draft' — giving comprehensive coverage of the task.

5 / 5

Completeness

Explicitly answers both 'what' (scan merged PRs, draft the entry, open a PR) and 'when' ('Use for a weekly or per-release changelog you no longer want to write by hand') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keywords ('changelog', 'pull requests', 'weekly or per-release changelog') but missing common synonyms users say like 'release notes'; a few natural terms absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (drafting changelogs from merged PRs into a PR) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Reviewed

Table of Contents