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 placeholder that repeats the skill name without explaining what the skill actually does or when it should be selected. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should activate it. The duplicate trigger term suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific capabilities such as 'Generates branch names following team conventions (e.g., feature/TICKET-123-short-description), validates branch name format, suggests names from Jira/issue titles'.
Add a 'Use when...' clause with natural trigger terms like 'name a branch', 'git branch name', 'branch convention', 'feature branch', 'bugfix branch', 'branch format'.
Remove the duplicate trigger term and replace the boilerplate 'Part of the DevOps Basics skill category' with actionable context about what distinguishes this skill from other DevOps skills.
| 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 naming conventions', or similar. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line just repeats the skill name rather than describing meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'branch naming helper' repeated twice. It misses natural user phrases like 'name a branch', 'git branch', 'branch convention', 'feature branch', or 'branch format'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'branch naming' is somewhat specific to a niche task, which reduces conflict risk slightly, but the lack of concrete detail means it could overlap with broader git or DevOps skills. | 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 a hollow template with no substantive content. It repeatedly describes itself in abstract terms ('provides automated assistance for branch naming helper tasks') without ever delivering any actual branch naming conventions, examples, regex patterns, or concrete guidance. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Replace the abstract capability descriptions with actual branch naming conventions (e.g., 'feature/<ticket>-<description>', 'bugfix/<ticket>-<description>') and provide concrete examples of valid and invalid branch names.
Add a concise reference table or list of branch prefixes (feature/, bugfix/, hotfix/, release/, chore/) with when to use each, plus a regex pattern for validation.
Include an executable example such as a git command: `git checkout -b feature/JIRA-123-add-user-auth` and show how to validate branch names with a git hook snippet.
Remove all meta-sections like 'When to Use', 'Example Triggers', and 'Capabilities' that describe the skill rather than teaching the actual content.
| 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 conventions, patterns, or rules. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no naming conventions, no examples of valid/invalid branch names, no commands, no patterns like 'feature/', 'bugfix/', 'hotfix/' prefixes. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow or steps are provided. The 'step-by-step guidance' is only mentioned as a capability claim but never actually delivered. There is no actionable sequence whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive wall of meta-descriptions with no meaningful structure, no references to detailed materials, and no useful organization of information. | 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
3e83543
- 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.