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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill branch-naming-helperActivation
7%This description is essentially a placeholder with no substantive content. It only states the skill name and category without describing any capabilities, use cases, or meaningful trigger terms. The repeated 'branch naming helper' as the only trigger term suggests auto-generated or incomplete metadata.
Suggestions
Add specific actions the skill performs, e.g., 'Generates standardized git branch names following team conventions, validates branch name formats, suggests prefixes (feature/, bugfix/, hotfix/)'
Include a 'Use when...' clause with natural trigger terms like 'Use when creating new branches, naming git branches, following branch naming conventions, or when user mentions feature branches, bugfix branches, or branch prefixes'
Remove the duplicate trigger term and add varied natural language triggers users would actually say: 'branch name', 'git branch', 'new branch', 'naming convention', 'branch prefix'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Branch Naming Helper' which is a name, not a description of what it does. No specific capabilities like 'generates branch names', 'validates naming conventions', or 'suggests prefixes' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no use cases or scenarios). The 'Triggers on' line just repeats the skill name and provides no meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'branch naming helper' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms users would say like 'branch name', 'git branch', 'naming convention', 'feature branch', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'branch naming' is a specific domain that wouldn't conflict with most skills, the lack of detail about what specifically this skill does (vs other git/DevOps skills) creates some ambiguity about when to select it over related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is essentially a placeholder with no actionable content. It describes what a branch naming helper should do without providing any actual branch naming conventions, examples, or guidance. The entire content could be replaced with a simple table of branch prefixes and a naming pattern example.
Suggestions
Add concrete branch naming conventions with examples (e.g., 'feature/JIRA-123-add-login', 'bugfix/fix-null-pointer', 'hotfix/v1.2.1-security-patch')
Include a decision tree or table mapping task types to branch prefixes (feature/, bugfix/, hotfix/, release/, chore/)
Provide regex patterns or validation rules for branch names that can be copy-pasted into git hooks
Remove all generic boilerplate sections ('Purpose', 'Capabilities', 'Example Triggers') and replace with actual naming rules and examples
| 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 doesn't need. | 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 provided. For a branch naming skill, there should be clear steps or a decision tree for choosing branch prefixes (feature/, bugfix/, hotfix/) and formatting conventions. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there's no actual content to disclose. The structure exists but serves no purpose since there's nothing substantive to navigate to. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.