changelog
Create changelog files for important commits in a PR
72
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
32%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 provides a basic understanding of the skill's purpose but is too terse to be effective for skill selection. It lacks explicit trigger guidance ('Use when...') which is critical for Claude to know when to select this skill. The description would benefit from more specific actions and natural trigger terms.
Suggestions
Add a 'Use when...' clause with trigger terms like 'changelog', 'release notes', 'PR summary', 'document changes', or 'what changed'
Expand the action list to include specifics like 'summarizes code changes', 'categorizes by type (features, fixes, breaking changes)', or 'formats for release notes'
Include common term variations such as 'pull request', 'change log', 'release documentation' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (changelog files, commits, PR) and one action (create), but lacks comprehensive detail about what the changelog contains or how it's structured. | 2 / 3 |
Completeness | Describes what it does (create changelog files) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'changelog', 'commits', and 'PR' that users might say, but misses common variations like 'pull request', 'release notes', 'change log', or 'version history'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'changelog' + 'PR' + 'commits' provides some distinctiveness, but could overlap with general git/commit message skills or documentation generation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%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-crafted skill that efficiently communicates changelog creation procedures with concrete examples and clear file naming conventions. The main weakness is the lack of validation steps - there's no guidance on verifying the changelog files are correctly formatted or handling potential issues. Overall, it's actionable and appropriately scoped for its purpose.
Suggestions
Add a validation step after creating changelog files, such as checking that files exist and follow the expected format
Include guidance on what to do if the changelog/ directory doesn't exist or if there are conflicts with existing changelog files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable guidance including the exact git command to run, specific file naming conventions, and complete examples of changelog file contents that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (check commits, create files, format content), but lacks validation checkpoints. No guidance on verifying changelog files were created correctly or handling edge cases like merge conflicts. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Instructions, Example). No external references needed and the structure is easy to follow. | 3 / 3 |
Total | 11 / 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.