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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill branch-naming-helper37
Quality
7%
Does it follow best practices?
Impact
90%
1.02xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/branch-naming-helper/SKILL.mdDiscovery
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger terms. It fails to help Claude understand when to select this skill, as it contains no concrete actions, no natural user language triggers, and no explicit 'Use when...' guidance.
Suggestions
Add specific actions the skill performs, e.g., 'Generates branch names following team conventions, validates branch name format, suggests names based on ticket/issue numbers'
Include natural trigger terms users would say: 'git branch', 'branch name', 'naming convention', 'feature branch', 'create branch', 'branch format'
Add an explicit 'Use when...' clause: 'Use when the user needs help naming git branches, asks about branch naming conventions, or wants to generate a branch name from a ticket number'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Branch Naming Helper' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'generates', 'validates', 'formats', or 'suggests' branch names. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use cases or triggers beyond the skill name itself). The 'Triggers on' clause just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'branch naming helper' repeated twice, which is the skill's own name rather than natural user language. Missing terms users would actually say like 'branch name', 'git branch', 'naming convention', 'create branch'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'branch naming' is somewhat specific to git/version control context, which provides some distinctiveness. However, the lack of detail about what it actually does could cause confusion with other git-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It describes what a branch naming helper skill would do without actually providing any branch naming conventions, patterns, or examples. The entire content could be replaced with a simple pattern like 'type/TICKET-description' with concrete examples.
Suggestions
Add concrete branch naming patterns (e.g., 'feature/JIRA-123-add-login', 'bugfix/GH-456-fix-null-pointer', 'hotfix/v1.2.1-security-patch')
Include a simple table or list showing branch type prefixes (feature/, bugfix/, hotfix/, release/) with when to use each
Provide 2-3 examples of good vs bad branch names to make the guidance immediately actionable
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual naming rules
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about branch naming. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no branch naming conventions, no examples of good/bad branch names, no patterns like 'feature/TICKET-123-description'. The skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. Branch naming is a simple task that could be explained in one clear pattern, but instead the content only describes when the skill activates without explaining what to actually do. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with clear headers, but there's no actual content to disclose. The structure exists but serves no purpose since there's nothing substantive to navigate to or reference. | 2 / 3 |
Total | 5 / 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 | |
- 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.