finish-branch
Use when implementation is complete, all tests pass, and the work needs to be integrated or finalized
70
Quality
57%
Does it follow best practices?
Impact
91%
1.93xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/finish-branch/SKILL.mdDiscovery
14%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 description critically fails to explain what the skill does, providing only vague timing guidance without any concrete capabilities. While it attempts to specify when to use the skill, the lack of specific actions (commit, merge, deploy, etc.) makes it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Creates git commits, opens pull requests, merges branches, or deploys code')
Include natural trigger terms users would say like 'commit', 'merge', 'PR', 'pull request', 'push', 'deploy', 'ship it'
Clarify the distinct niche - is this for git operations, CI/CD, deployment, or something else? Be explicit to avoid conflicts with other skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only vague terms like 'integrated or finalized' without specifying what actions are performed (e.g., git commit, merge, deploy, PR creation). | 1 / 3 |
Completeness | The description only addresses 'when' (via the 'Use when...' clause) but completely fails to explain 'what' the skill actually does - there are no capabilities described. | 1 / 3 |
Trigger Term Quality | Contains some relevant terms like 'tests pass', 'implementation complete', and 'integrated' that users might mention, but misses common variations like 'commit', 'merge', 'PR', 'push', 'deploy', or 'ship'. | 2 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'integrated or finalized' could apply to many different skills (git operations, deployment, documentation, code review, etc.) making it highly prone to conflicts. | 1 / 3 |
Total | 5 / 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 exemplary skill file that demonstrates excellent structure and actionability. It provides clear, numbered options with executable commands, includes proper validation checkpoints (test verification, discard confirmation), and maintains appropriate boundaries by delegating to sub-skills. The quick reference table and common mistakes sections add value without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only necessary information. It assumes Claude's competence with git commands and doesn't explain basic concepts. Every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable bash commands, specific option text to present, and concrete staging guidance. The workflow is copy-paste ready with clear conditionals for different scenarios. | 3 / 3 |
Workflow Clarity | Excellent multi-step sequencing with explicit validation checkpoints (test verification before proceeding, confirmation before discard). Clear feedback loops with 'Stop. Don't proceed to Step 2' and typed confirmation requirements. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Process steps, Quick Reference, Common Mistakes, Red Flags, Integration). References to sub-skills (kit:create-pr, kit:worktree-cleanup) are one level deep and clearly signaled. | 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
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.