CtrlK
BlogDocsLog inGet started
Tessl Logo

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured instruction skill with concrete examples and a clear numbered workflow. It is strong on progressive disclosure and solid on actionability, conciseness, and workflow clarity, with the main limitation being the lack of explicit validation/feedback checkpoints in the writing process.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — principles, a category taxonomy, example transformations, and a template — with only minor instances (the full structure template block) that could be trimmed, fitting the 4 anchor rather than the lean 5.

4 / 5

Actionability

Provides concrete, actionable guidance — a categorization scheme, writing principles, two explicit technical→user-facing example transformations, and a copy-ready structure template — but the actual prose drafting is governed by principles rather than fully prescribed, matching the 4 anchor.

4 / 5

Workflow Clarity

A clear numbered sequence (gather → categorize → write → structure → adjust tone) with well-defined steps; this is a generation task with no destructive/batch operations, so the absence of validation checkpoints does not trigger the cap, but it also lacks explicit feedback loops, capping it at 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is a single concise file (~58 lines) with no need for external references (no references/scripts/assets bundles exist), and it is cleanly organized into Context and numbered Instructions sections, satisfying the simple-skill exception that allows a 5 with just well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

95%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 explicitly covers both capability and trigger conditions with natural, varied phrasing. The only soft spot is specificity, where the action list is solid but not maximally comprehensive.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Generate user-facing release notes from tickets, PRDs, or changelogs', 'Creates clear, engaging summaries organized by category'), but the action list is not exhaustive, leaving minor coverage gaps consistent with the 4 anchor rather than 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Generate user-facing release notes... Creates clear, engaging summaries organized by category') and 'when' ('Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms users actually say — 'writing release notes', 'creating changelogs', 'announcing product updates', 'summarizing what shipped' — matching the 5 anchor for varied natural phrasing; file extensions are N/A for this domain.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (release-notes generation) with distinct, specific triggers ('changelogs', 'announcing product updates') that are unlikely to fire for unrelated skills, matching the 5 anchor for minimal conflict risk.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-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.