branch-naming-helper
Branch Naming Helper - Auto-activating skill for DevOps Basics. Triggers on: branch naming helper, branch naming helper Part of the DevOps Basics skill category.
34
3%
Does it follow best practices?
Impact
90%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/branch-naming-helper/SKILL.mdQuality
Discovery
7%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 is essentially a title repeated with boilerplate metadata. It fails to describe any concrete actions, lacks natural trigger terms users would say, and provides no guidance on when Claude should select this skill. It reads more like an auto-generated stub than a functional skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates standardized git branch names from ticket IDs, enforces naming conventions (feature/, bugfix/, hotfix/ prefixes), and validates branch names against team patterns.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about git branch names, naming conventions, branch formats, or needs help creating a branch name from a Jira ticket or issue number.'
Remove the redundant duplicate trigger term ('branch naming helper' listed twice) and replace with varied natural language terms users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('branch naming') but describes no concrete actions. There are no specific capabilities listed like 'generates branch names from ticket IDs', 'validates branch name format', or similar. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of actual functionality beyond the title. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'branch naming helper' repeated twice. It lacks natural user terms like 'git branch name', 'naming convention', 'feature branch', 'branch format', or 'create branch'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'branch naming' is somewhat specific and unlikely to conflict with many other skills, but the lack of detail about what it actually does (e.g., generating names vs. validating names vs. enforcing conventions) makes it only moderately distinctive. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content. It consists entirely of boilerplate meta-descriptions about what the skill would do, without providing any branch naming conventions, examples, patterns, or actionable guidance. It fails on every dimension because it contains no substantive information.
Suggestions
Replace the meta-description with actual branch naming conventions (e.g., `feature/TICKET-123-short-description`, `bugfix/TICKET-456-fix-login`, `hotfix/v1.2.1-critical-patch`) with concrete examples.
Add a concise reference table of branch type prefixes (feature/, bugfix/, hotfix/, release/, chore/) with when to use each.
Include a validation pattern or regex (e.g., `^(feature|bugfix|hotfix|release|chore)/[A-Z]+-[0-9]+-[a-z0-9-]+$`) that Claude can use to check branch names.
Remove all 'Purpose', 'When to Use', 'Capabilities', and 'Example Triggers' boilerplate sections—these waste tokens and provide no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual branch naming guidance. Every section restates the same vague idea. | 1 / 3 |
Actionability | There are zero concrete instructions, no naming conventions, no examples of actual branch names, no patterns, no code, and no commands. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow or steps are provided. The 'step-by-step guidance' mentioned in Capabilities is never actually delivered. There is no sequence of actions for Claude to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no meaningful structure. There are no references to detailed files, no examples section, and no organized content hierarchy. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.