CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

generate-release-notes

generate-release-notes

Quality

61%

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

Quality

Content

68%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 admirably lean, with a concrete prerequisite-and-recovery path and a well-signaled external writing guide. However, the core workflow is underspecified — the tool-to-purpose mapping and the location of the release notes file to update are missing, leaving the actual execution to inference.

Suggestions

State which tool provides what, e.g., "Call getCurrentMilestone for the current milestone name and getReleaseFeatures for the list of features."

Specify the path or location of the release notes file to update, plus any expected section format or convention.

Add a light step ordering (fetch milestone → fetch features → draft using the instructions file → update the release notes file) so the workflow does not rely on inference.

DimensionReasoningScore

Conciseness

The body is two lean paragraphs with zero padding: the prerequisite names the exact tools ("getCurrentMilestone" and "getReleaseFeatures"), the recovery command ("Extensions: Show Recommended Extensions"), and the extension path (".vscode/extensions/doc-assistant/"), while the task itself is a single sentence. Every token earns its place and nothing needs trimming, matching the anchor-5 example.

5 / 5

Actionability

Concrete elements exist (named tools, an exact Command Palette command, the extension install path, and the linked instructions file), but key execution details are missing: the body never says which tool yields the feature list vs. the milestone, or where "the release notes file" is located. This lands on anchor 3 ("some concrete guidance but incomplete") rather than anchor 4, whose guidance is mostly executable.

3 / 5

Workflow Clarity

The prerequisite availability check with an explicit install fallback is a genuine checkpoint with a recovery path, which lifts it above anchor 2's absent validation. However, the core sequence (fetch milestone → fetch features → draft → update file) is left implicit with no validation of the result, and the single action is not unambiguous (the target file is unspecified), so the simple-skill path to a 5 does not apply.

3 / 5

Progressive Disclosure

The body is a short overview with one clearly signaled, one-level-deep reference ("Use [release notes writing instructions file](../../instructions/release-notes-writing.instructions.md) as a guide"), and nothing that belongs in a separate file is inlined. It falls just short of anchor 5 because the referenced guide lives outside the skill bundle (../../instructions/) and the skill has no bundle structure of its own — a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

36%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 just the skill name repeated as a slug — it states a single implied action with no "when" guidance, no synonyms, and no mention of the file-update half of the task. It needs a full rewrite into a sentence covering both actions plus an explicit "Use when..." trigger clause.

Suggestions

Rewrite the description as a sentence covering both actions, e.g., "Generates release notes for the features the user worked on in the current release and updates the release notes file."

Add an explicit trigger clause, e.g., "Use when the user asks for release notes, a changelog, or a summary of shipped work for the current milestone."

Include natural synonyms such as "changelog", "ship notes", or "release summary" to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description is the bare slug "generate-release-notes": it names the domain with a single implied action, comparable to the anchor-2 example "Processes PDF files". It omits the second half of the task (updating the release notes file), so it does not reach anchor 3's "1-2 concrete actions".

2 / 5

Completeness

The description offers only a thin "what" ("generate-release-notes") with no "when" clause at all — not even implied trigger guidance. It fits anchor 2 ("vague 'what' and no 'when'") better than anchor 3, whose example states a clear, multi-action "what"; this one omits the file-update part of the task entirely.

2 / 5

Trigger Term Quality

"release notes" is the natural phrase a user would actually say, matching anchor 3's "some relevant keywords" rather than anchor 2's generic keywords. However, no variations or synonyms (e.g., "changelog", "release summary") are present, so it falls short of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The release-notes niche is fairly specific, so it is not the broad overlap of anchor 2, but the bare slug provides no trigger context and could overlap with closely related skills such as changelog or commit-message generation. That matches anchor 3 ("somewhat specific but could still overlap") rather than anchor 4's clearly articulated distinct triggers.

3 / 5

Total

10

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode-docs

Path

.github/skills/generate-release-notes/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.