changelog-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill changelog-generatorChangelog Generator - Auto-activating skill for Technical Documentation. Triggers on: changelog generator, changelog 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 repeats the skill name as trigger terms and fails to describe any actual capabilities or use cases. The description would be nearly useless in a multi-skill environment where Claude needs to distinguish between options.
Suggestions
Add concrete actions the skill performs, such as 'Generates changelog entries from git commits, formats version history, creates CHANGELOG.md files following Keep a Changelog format'
Include a 'Use when...' clause with natural trigger terms like 'release notes', 'version history', 'what changed between versions', 'CHANGELOG.md', 'document changes'
Remove the redundant duplicate trigger term and expand to cover variations users would naturally say when needing changelog functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Changelog Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of parsing commits, formatting entries, comparing versions, 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 the skill name repeated. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'changelog generator' repeated twice, which is redundant and extremely narrow. Missing natural variations users would say like 'release notes', 'version history', 'what changed', 'CHANGELOG.md', or 'update log'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'changelog generator' is fairly specific to a niche task, which provides some distinctiveness. However, the lack of detail about what differentiates it from general documentation or release note skills creates potential overlap. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains zero actionable information about changelog generation - no format specifications, no code examples, no workflow steps, and no concrete guidance. The entire content could be replaced with 'This skill helps with changelog generation' and convey the same (lack of) information.
Suggestions
Add a concrete changelog format example (e.g., Keep a Changelog format) with actual markdown showing version entries, categories like Added/Changed/Fixed/Removed
Provide executable code or commands for generating changelogs from git commits (e.g., using conventional commits, git log parsing, or changelog generation tools)
Define a clear workflow: 1) gather commits since last release, 2) categorize changes, 3) format entries, 4) validate output structure
Include specific examples of input (git commits or PR descriptions) and expected output (formatted changelog entries)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about changelog 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 specific commands, no actual changelog format or generation steps. 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 a changelog, no validation checkpoints, and no process to follow. The skill merely lists vague 'capabilities' without any actionable sequence. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no links to related documentation. It's neither a useful overview nor does it point anywhere useful. | 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.