CtrlK
BlogDocsLog inGet started
Tessl Logo

vscode-release-notes-writer

Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.

56

Quality

63%

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

Quality

Content

61%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 well-organized and actionable, with concrete CLI commands, templates, and clear input-parameter gating. Its weaknesses are duplicated descriptive prose and the absence of explicit validation checkpoints for the batch release-note generation workflow.

Suggestions

Add a validation/verification step (e.g. confirm the generated TOC matches the H2 date sections and verify each issue summary links to its GH issue) to lift workflow clarity above the cap.

De-duplicate the Insiders/Stable overview descriptions that appear both in the intro and under each section to improve conciseness.

Clarify or inline the referenced templates/examples, or note that they reside outside the skill bundle, so navigation expectations are unambiguous.

DimensionReasoningScore

Conciseness

The content is mostly efficient with concrete commands and templates, but the Insiders and Stable descriptions are restated nearly verbatim in both the intro and their dedicated sections, which could be tightened.

3 / 5

Actionability

Provides a concrete executable `gh search issues` command, explicit file path formats (`v<version>.md`), template links, and required image filenames, leaving only minor gaps in execution detail.

4 / 5

Workflow Clarity

Steps are clearly numbered with input-gating checkpoints ('DO NOT continue until...'), but the batch issue-fetching and release-note-writing operation lacks explicit validation/verification feedback loops, so workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Well-structured with clearly signaled one-level references to templates and a concrete example, though the referenced files live outside the bundle (no local references/ or scripts/ files exist).

4 / 5

Total

14

/

20

Passed

Description

66%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 distinctive, clearly naming the VS Code release-note domain and the writing/reviewing actions it supports. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits completeness.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when generating or reviewing VS Code Insiders or Stable release notes from GitHub issues and PRs.' to make the trigger explicit and lift completeness.

Include natural user phrasings or synonyms (e.g. 'VS Code changelog', 'release notes draft') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (VS Code release notes) and two concrete actions ('writing and reviewing') across two artifact types (Insiders and Stable), showing several specific capabilities with minor gaps in coverage.

4 / 5

Completeness

It clearly answers 'what' (writing and reviewing Insiders/Stable release notes) but provides no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms like 'release notes', 'Insiders', 'Stable', and 'Visual Studio Code' that users would say, though it omits a few common variations and explicit trigger phrasing.

4 / 5

Distinctiveness Conflict Risk

Targets a clearly distinct niche (VS Code Insiders/Stable release notes) with minimal overlap risk against other skills, with only minor overlap with general docs-writing skills.

4 / 5

Total

15

/

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

relative_links

Relative link issues: 3 missing, 2 suspicious

Warning

Total

15

/

16

Passed

Repository
foryourhealth111-pixel/Vibe-Skills
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.