release-notes-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill release-notes-generatorRelease Notes Generator - Auto-activating skill for Technical Documentation. Triggers on: release notes generator, release notes generator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It merely restates the skill name as both the description and trigger terms, without explaining what the skill actually does or providing meaningful guidance on when to use it. The description fails on all core dimensions needed for effective skill routing.
Suggestions
Add specific actions the skill performs, such as 'Generates release notes by analyzing git commits, categorizing changes (features, fixes, breaking changes), and formatting them in standard changelog format'
Include a 'Use when...' clause with natural trigger terms like 'changelog', 'version notes', 'what changed', 'release summary', 'new version documentation'
Remove the redundant duplicate trigger term and expand with variations users would naturally say when needing this skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Release Notes Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of analyzing commits, formatting changes, categorizing updates, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a circular reference to the skill name. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'release notes generator' repeated twice, which is redundant and overly narrow. Missing natural variations users would say like 'changelog', 'version notes', 'what's new', 'release summary', or 'update log'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'release notes' is somewhat specific to a particular documentation type, which provides some distinctiveness. However, the vague 'Technical Documentation' category could overlap with other documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely placeholder boilerplate with zero actionable information about generating release notes. It describes capabilities it doesn't deliver and provides no concrete guidance, examples, templates, or workflows. The content would be identical if you replaced 'release notes generator' with any other task name.
Suggestions
Add a concrete release notes template with sections (e.g., Breaking Changes, New Features, Bug Fixes, Deprecations) and example entries
Provide executable code or commands for extracting changes from git commits, PRs, or issue trackers
Include a clear workflow: 1) Gather changes 2) Categorize by type 3) Write user-facing descriptions 4) Validate format
Add example input (git log, PR list) and expected output (formatted release notes) to make the skill actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about release notes generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code examples, no templates, no specific commands, no actual release notes format or structure. The content describes what the skill supposedly does without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating release notes, no process for gathering changes, no validation of output format. The 'step-by-step guidance' mentioned is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure for actual learning. No references to detailed materials, examples, or templates. The 'Related Skills' section provides no actionable navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.