release-notes-writer
Transforms a changelog or commit range into user-friendly release notes with highlights, upgrade guidance, and narrative framing. Use when publishing a release announcement, when the changelog is too dense for users to read, or when the user needs a blog-post-shaped summary of a version.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill release-notes-writer100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly articulates specific capabilities (transforming changelogs into release notes with highlights and upgrade guidance), provides excellent trigger coverage with natural user terms, and explicitly states when to use it with multiple concrete scenarios. The description is distinctive enough to avoid conflicts with related skills like commit message generation or general documentation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Transforms a changelog or commit range', 'user-friendly release notes', 'highlights', 'upgrade guidance', and 'narrative framing'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what ('Transforms a changelog or commit range into user-friendly release notes with highlights, upgrade guidance, and narrative framing') AND when ('Use when publishing a release announcement, when the changelog is too dense for users to read, or when the user needs a blog-post-shaped summary'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'changelog', 'commit range', 'release notes', 'release announcement', 'blog-post', 'version'. Good coverage of terms across different user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on release notes generation from changelogs/commits. Distinct from general documentation skills or commit message skills through specific triggers like 'release announcement', 'changelog too dense', and 'blog-post-shaped summary'. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Excellent skill that treats release notes as a craft with clear methodology. The headline pattern table, ruthless highlight selection criteria, and before/after demonstration requirement are all highly actionable. The worked example showing changelog→release notes transformation is particularly effective at teaching the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No explanation of what release notes are conceptually—jumps straight to actionable patterns. The worked example is necessary for demonstration, not padding. | 3 / 3 |
Actionability | Provides concrete templates, exact headline patterns by release type, specific before/after examples, and a complete worked example showing input→output transformation. Copy-paste ready structure. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (find headline → pick highlights → write before/after) with explicit decision criteria at each step. The 'Do not' section serves as validation guardrails. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Input, Shape, Steps 1-3, Upgrade notes, Worked example, Do not, Output format). References change-log-generator appropriately. Content is appropriately sized for a single file. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.