CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-note-generation

Toolkit for generating PowerToys stable or preview release notes from GitHub milestones, commit ranges, or Azure DevOps release-candidate builds. Prepare draft preview releases with three-component GitHub tags while preserving four-component build and asset versions. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare a draft preview release, calculate PR deltas across main and stable, update release documentation, manage PR milestones, or prepare and validate release assets.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-orchestrated overview: lean tables, explicit lazy-loading instructions, concrete conventions with worked examples, and real validation gates including a dedicated draft-verification script. It uniformly sits at score 4 — strong but with identifiable gaps: a dead reference link, a redundant workflow diagram, and a two-level scenario reference chain. Fixing the broken Instruction.md link and collapsing the diagram/table duplication would lift conciseness and progressive disclosure toward the top anchors.

Suggestions

Remove or fix the dead link to ./references/Instruction.md ("Legacy full documentation") — the file does not exist in the bundle, so navigation fails at that reference.

Delete either the ASCII workflow diagram or the step table in "Workflow Overview" — they duplicate the same 1.0→4.2 sequence and together cost ~40 lines of token budget.

Inline one copy-paste-ready example invocation per common case (e.g., a sample `dump-prs-since-commit.ps1` or `upsert-draft-preview-release.ps1` call with typical arguments) so the body is executable without opening a step file.

DimensionReasoningScore

Conciseness

The body is dense and efficient — tables for steps, scripts, and troubleshooting; no explanations of concepts Claude already knows; conventions are compact rules with a worked example ("build `0.102.2991.0` maps to tag `v0.102.2991`"). The one trim candidate is the ~40-line ASCII workflow diagram, which duplicates the step sequence already conveyed by the "Workflow Overview" table directly below it — a minor instance of padding, matching score 4 rather than the lean score-5 anchor or the noticeably-verbose score-3 anchor.

4 / 5

Actionability

Concrete guidance throughout: verification commands ("Run `gh auth status` to verify; if not logged in, run `gh auth login` first"), exact output paths, a per-script purpose table, and specific conventions like "Pass `-ReleaseTag $context.tag` when preparing asset download links". It stops short of fully copy-paste-ready script invocations — those are deferred to the step references — so it fits score 4 (mostly executable with minor gaps) rather than score 5.

4 / 5

Workflow Clarity

Steps are clearly sequenced (1.0 → 4.2 diagram plus an ordered table) with several explicit checkpoints: "`gh auth status` must pass", "auto-suggest + human label low-confidence", "human reviews" after batch grouped_md generation, and preview-mode verification via `verify-draft-preview-release.ps1` plus `final-review.md`. It is not score 5 because validation details for batch metadata writes (milestone assignment, labeling) are deferred to the step files rather than stated as explicit validate/fix/retry loops in the body; the existing gates (prereq verification, human labeling review, draft verification, final review) keep it above the score-3 validation-gap cap.

4 / 5

Progressive Disclosure

Good structure scored against the actual bundle: SKILL.md is a genuine overview with well-signaled references ("Do not read all steps at once—only read the step you are executing", a scenario router table, a step-doc list, a scripts table), and all linked paths exist except one. Two issues keep it from score 5: the "[Detailed Instructions](./references/Instruction.md) - Legacy full documentation" link points to a file that does not exist in the bundle, and the scenario chain nests two-plus levels deep (SKILL.md → scenarios/index.md → preview-release.md → preview-draft-safety.md / preview-reporting.md), where the top anchor calls for one-level-deep references.

4 / 5

Total

16

/

20

Passed

Description

100%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 a model example: third-person voice, concrete capabilities tied to specific data sources, and an explicit "Use when asked to..." clause enumerating eight natural trigger phrases with synonyms (release notes / changelog / release documentation). Every dimension lands on the top anchor. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: "generating PowerToys stable or preview release notes from GitHub milestones, commit ranges, or Azure DevOps release-candidate builds", "Prepare draft preview releases with three-component GitHub tags while preserving four-component build and asset versions", plus "calculate PR deltas", "manage PR milestones", and "prepare and validate release assets". This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage); score 4 would require noticeable gaps in coverage, but collection, summarization, deltas, milestones, releases, and assets are all named.

5 / 5

Completeness

Explicitly answers both questions: the what ("Toolkit for generating PowerToys stable or preview release notes... Prepare draft preview releases with three-component GitHub tags...") and the when ("Use when asked to create release notes, summarize milestone PRs, generate changelog..." with concrete trigger phrases). This mirrors the score-5 anchor example almost exactly; the explicit "Use when" clause rules out the score-3 cap.

5 / 5

Trigger Term Quality

The trigger list covers natural user phrasings with synonyms: "create release notes", "summarize milestone PRs", "generate changelog", "update release documentation", "prepare a draft preview release", "calculate PR deltas across main and stable", "manage PR milestones", "prepare and validate release assets". Synonym coverage (release notes / changelog / release documentation) matches the comprehensive score-5 anchor rather than the "a few natural terms missing" score-4 anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — "PowerToys", "Azure DevOps release-candidate builds", "three-component GitHub tags", "PR deltas across main and stable" — so it would not trigger for unrelated release-notes or general GitHub skills. Clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

20

/

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 missing, 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

microsoft/PowerToys

Path

.github/skills/release-note-generation/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.