release-notes
Generate release notes between two git tags with categorized PR summaries and author attribution
83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 description with excellent specificity and natural trigger terms that developers would use. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The description clearly carves out a distinct niche in release note generation.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks for release notes, changelog generation, version summaries, or comparing changes between tags/releases'
Consider adding file format mentions if applicable (e.g., 'outputs markdown release notes') to further clarify the output
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate release notes', 'between two git tags', 'categorized PR summaries', and 'author attribution'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the what. | 2 / 3 |
Trigger Term Quality | Contains natural keywords users would say: 'release notes', 'git tags', 'PR summaries', 'author attribution'. These are terms developers naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: release notes generation specifically between git tags with PR categorization. Unlikely to conflict with general git or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with clear workflow steps and validation checkpoints. The concrete git/gh commands make it immediately executable. Minor improvements could be made by tightening some verbose explanations and potentially splitting the detailed categorization rules into a separate reference file.
Suggestions
Tighten the categorization rules section - the criteria lists could be more concise (e.g., bullet points instead of prose explanations)
Consider moving the detailed 'Formatting rules' and categorization criteria to a separate REFERENCE.md file, keeping only a summary in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what 'LOWER' means multiple times, verbose categorization rules). Some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides concrete, executable git and gh commands throughout. Each step has specific commands with exact syntax, making it copy-paste ready for implementation. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 1-9), explicit validation checkpoints (tag validation, user approval before writing), and error handling instructions. The approval gate before writing is a good feedback loop. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document. The categorization rules and formatting rules could potentially be split into separate reference files for a cleaner overview, though the current length is manageable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.