CtrlK
BlogDocsLog inGet started
Tessl Logo

release-notes

Generate release notes between two git tags with categorized PR summaries and author attribution

65

Quality

79%

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 ./.claude/skills/release-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is a tightly written, highly actionable multi-step workflow with strong validation checkpoints and an approval gate; its only weakness is minor over-explanation in the categorization rules and the lack of any external reference structure.

Suggestions

Tighten the categorization rules by consolidating the prose into a compact lookup table to reduce token overhead.

Consider extracting the long output template and category rules into a referenced file so the overview stays leaner.

Add a brief upfront summary of inputs/outputs so the workflow shape is visible before the detailed steps.

DimensionReasoningScore

Conciseness

The body is procedural and direct with no padding about concepts Claude already knows; minor over-explanation in the categorization rules keeps it just below a 5.

4 / 5

Actionability

It provides concrete, copy-paste-ready commands (git tag -l, git log --oneline LOWER..TAG, gh pr view ... --json ..., gh search prs ...) plus an exact output template covering the common cases.

5 / 5

Workflow Clarity

Nine clearly sequenced steps include explicit validation checkpoints (tag and LOWER existence, "verify the total count matches", an approval gate before writing), satisfying the batch-operation validation requirement and matching the anchor with feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized with clear section headers and easy navigation; it is a 4 rather than 5 because there are no one-level-deep references to evaluate (none are needed here).

4 / 5

Total

18

/

20

Passed

Description

70%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 distinct, naming concrete actions and natural trigger terms, but it omits any explicit "Use when..." guidance, which caps its completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when generating release notes or a changelog between two git tags."

Include common synonyms such as "changelog" or "version notes" to broaden natural keyword coverage.

Mention the supported workflow context (e.g. GitHub PRs) so the trigger is unambiguous to users.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Generate release notes", "categorized PR summaries", and "author attribution" over a defined domain ("between two git tags"), matching the anchor for several specific actions with minor coverage gaps; not a 5 because the action list is not comprehensive.

4 / 5

Completeness

The description clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3; it is not a 4 because the "when" is entirely missing rather than weakly implied.

3 / 5

Trigger Term Quality

"release notes", "git tags", and "PR summaries" are natural phrases a user would say, giving good keyword coverage; not a 5 because synonyms like "changelog" or "version notes" are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — release notes generated from two git tags with categorized PR summaries and author attribution — with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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.

Validation15 / 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
dlt-hub/dlt
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.