repo-changelog
Generates end-user friendly release notes and changelogs by analyzing git diffs, consolidating changes, and formatting for Slack and documentation
63
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 strong description with excellent specificity and natural trigger terms that users would actually say. 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 around release notes and changelogs.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'when the user asks for release notes, changelogs, version summaries, or wants to communicate changes to end users'
Consider adding file extension triggers like '.md changelog' or mentioning 'CHANGELOG.md' as a common artifact
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generates end-user friendly release notes and changelogs', 'analyzing git diffs', 'consolidating changes', and 'formatting for Slack and documentation'. | 3 / 3 |
Completeness | Clearly answers 'what' (generates release notes by analyzing diffs and formatting output), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'release notes', 'changelogs', 'git diffs', 'Slack', 'documentation'. These are terms users naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on release notes/changelogs with distinct triggers like 'Slack', 'end-user friendly', and 'changelogs'. Unlikely to conflict with general git or documentation skills due to specific output format focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like product documentation than an actionable skill for Claude. It thoroughly explains what the tool does and its capabilities, but fails to provide executable code or commands that Claude can actually run. The verbose explanations of obvious concepts (categories, markdown formatting, git basics) waste tokens without adding value.
Suggestions
Add executable code examples showing how to invoke the scripts (e.g., `python git_analyzer.py --from-tag v1.0.0 --to-tag v1.1.0`)
Remove explanatory content about concepts Claude already knows (what git diffs are, what markdown is, what each category means)
Add validation steps and error handling guidance (e.g., 'If tag not found: run `git tag -l` to list available tags')
Move the detailed tables and 'When to Use' sections to a separate reference file, keeping SKILL.md focused on quick-start execution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant verbosity explaining concepts Claude already knows (what git diffs are, how categories work, what markdown is). The 'How the Analysis Works' section explains basic processing steps that don't add actionable value, and tables like 'Output Categories' over-explain obvious concepts. | 2 / 3 |
Actionability | Despite listing scripts like 'git_analyzer.py' and 'diff_parser.py', there's no executable code showing how to use them. The skill describes what it does conceptually but provides no actual commands, function calls, or copy-paste ready examples for Claude to execute. | 1 / 3 |
Workflow Clarity | The 'How the Analysis Works' section provides a 6-step sequence, but lacks validation checkpoints or error handling. There's no guidance on what to do if git commands fail, tags don't exist, or diffs are too large - just a mention in 'Limitations' without recovery steps. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one large file. The scripts are mentioned but not linked to documentation. Tables and extensive examples could be moved to reference files, with SKILL.md serving as a leaner overview. | 2 / 3 |
Total | 7 / 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.