Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
87
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
67%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 is concise and specific about what it does, clearly naming the action (cleaning merged branches) and the constraints (keeping main, dev, gh-pages). Its main weakness is the lack of an explicit 'Use when...' clause and missing some natural trigger terms like 'git' or 'delete branches' that users might say.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to clean up, prune, or delete old git branches.'
Include additional trigger terms like 'git', 'delete branches', 'prune branches', 'stale branches' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: 'clean up merged branches locally and on remote' and specifies which branches to keep ('main, dev, and gh-pages'). These are specific, actionable details. | 3 / 3 |
Completeness | Clearly answers 'what' (clean up merged branches locally and on remote, keeping specific branches), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'merged branches', 'remote', 'main', 'dev', 'gh-pages' which are natural git terms, but misses common variations like 'git', 'prune', 'delete branches', 'stale branches', or 'branch cleanup'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: cleaning up merged git branches with a defined set of protected branches. Unlikely to conflict with other skills due to the narrow, well-defined scope. | 3 / 3 |
Total | 10 / 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 a well-crafted skill that provides clear, actionable git branch cleanup instructions with appropriate safety guardrails. The workflow includes explicit confirmation steps before destructive operations (especially remote deletes) and handles edge cases like unmerged branches. The summary table at the end provides good verification of the operation's results. One minor issue: the first grep command appears to have an unclosed quote in the regex pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose—no explanation of what git branches are or how git works. The skill assumes Claude's competence and focuses purely on the specific task steps and constraints. | 3 / 3 |
Actionability | Provides concrete, executable bash commands for each step, specific branch exclusion patterns, and a clear output format (summary table). Commands are copy-paste ready with only the variable parts parameterized. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit safety checkpoints: reporting before deletion, user confirmation before remote deletes, refusing to force-delete without approval, and skip conditions when no branches are found. The feedback loop for unmerged branches is well-handled. | 3 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines that is well-organized with numbered steps and clear section headers. No external references are needed, and the content is appropriately scoped. | 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.
Reviewed
Table of Contents