changelog-creator
Changelog Creator - Auto-activating skill for DevOps Basics. Triggers on: changelog creator, changelog creator Part of the DevOps Basics skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill changelog-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped and essentially non-functional for skill selection. It provides no information about what the skill actually does, relies on redundant trigger terms, and lacks any guidance on when Claude should use it. The description reads more like a category label than a useful skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Generates changelogs from git commit history, formats release notes, tracks version changes between releases'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks about changelogs, release notes, version history, CHANGELOG.md, or tracking changes between versions'
Remove the redundant trigger term and expand to include variations users would naturally say such as 'release notes', 'what's new', 'version updates', 'commit summary'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Changelog Creator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating, generating, formatting, or any specific changelog-related operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use-case guidance). The 'Triggers on' line is not a proper 'Use when...' clause and only repeats the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'changelog creator' repeated twice, which is redundant and overly narrow. Missing natural variations users would say like 'changelog', 'release notes', 'version history', 'what changed', or 'generate changelog'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'changelog' is somewhat specific to a particular domain, which provides some distinctiveness. However, without describing what specifically this skill does with changelogs, it could conflict with other documentation or DevOps skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with no actual instructional value. It describes what a changelog creator skill would do without providing any concrete guidance, code examples, format specifications, or workflows for actually creating changelogs. The content is essentially a placeholder that teaches Claude nothing about changelog creation.
Suggestions
Add concrete changelog format examples (e.g., Keep a Changelog format, Conventional Commits integration) with actual markdown templates
Include executable code or commands for generating changelogs from git history (e.g., git log parsing, conventional-changelog CLI usage)
Define a clear workflow: 1) gather commits since last release, 2) categorize changes, 3) format output, 4) validate against schema
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'automated assistance for changelog creator tasks' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no actual instructions on how to create a changelog. The content describes what the skill supposedly does without providing any executable steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or processes described for creating changelogs. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, examples, or related documentation that would help with actual changelog creation. | 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.