pr-changelog
Generate a CHANGELOG entry line for a pull request from code changes. Use when the user asks to write a changelog entry, fill the changelog section of a PR, or determine if changes are user-facing.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 skill description that clearly communicates what the skill does and when to use it. It uses third person voice, includes an explicit 'Use when' clause with natural trigger terms, and targets a well-defined niche that is unlikely to overlap with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: 'Generate a CHANGELOG entry line', 'write a changelog entry', 'fill the changelog section of a PR', and 'determine if changes are user-facing'. These are multiple distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate a CHANGELOG entry line from code changes) and 'when' (explicit 'Use when' clause covering writing changelog entries, filling PR changelog sections, or determining if changes are user-facing). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'CHANGELOG', 'changelog entry', 'pull request', 'PR', 'code changes', 'user-facing'. These cover common variations of how a user would phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — CHANGELOG entry generation for PRs — with distinct triggers like 'changelog entry', 'changelog section of a PR', and 'user-facing changes'. This is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill. It is concise, actionable, and clearly structured with a decision tree, exact format requirements, CI context, and concrete examples. The content respects Claude's intelligence while providing all the project-specific knowledge needed to generate correct changelog entries.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what a changelog is or how PRs work. The decision tree, rules, and examples all earn their place. | 3 / 3 |
Actionability | Provides the exact format string, a concrete decision tree (user-facing yes/no), a specific git command to run, and multiple real-world examples of both positive and null entries. Copy-paste ready. | 3 / 3 |
Workflow Clarity | The 4-step process is clearly sequenced and unambiguous. For this simple, non-destructive task (writing a single line), no validation/feedback loop is needed. The decision logic is explicit with clear branching. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized into logical sections (Format, Decision, Rules, Steps, Examples) with no need for external references. Navigation is easy. | 3 / 3 |
Total | 12 / 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.
- Repository
- MetaMask/metamask-mobile
- Commit
bee9b14
- 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.