branch-namer

Generate descriptive git branch names that follow the project's naming convention. Use this skill whenever the user asks to create a branch, name a branch, start working on a feature or fix, checkout a new branch, or when you're about to run `git checkout -b` or `git switch -c`. Also trigger when you see a vague branch name like `fix/auth` or `feature/billing` that lacks a description of what's actually changing — the branch name should always tell you *what* the change does, not just its category.

1.14x

Quality

91%

Does it follow best practices?

Impact

93%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Excellent instructional content: concrete format rules, a project-specific release-behavior table, strong worked examples, and a clear workflow with check steps. The only improvement area is trimming the brief motivational 'Problem' section for token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dense and focused on project-specific knowledge Claude cannot infer (the CI/CD type-release table, the .commitlintrc.json scope-enum workflow), but the short 'The Problem' section is motivational framing that could be trimmed. Not a 5 due to that minor padding; not a 3 because nothing explains concepts Claude already knows.	4 / 5
Actionability	Fully actionable for an instruction-only skill: an exact format template '<type>/<scope>-<descriptive-slug>', a specific file to read ('.commitlintrc.json'), concrete slug-writing rules, and a nine-row bad-to-good example table covering the common cases. Not a 4 because no key detail is missing for executing the task.	5 / 5
Workflow Clarity	A clear six-step sequence with checkpoints ('Check the total length', 'Suggest the branch name to the user before creating it'), and it is a simple single-task, non-destructive skill so no validation cap applies. Not a 4 because the sequence is unambiguous and includes explicit check-and-confirm steps.	5 / 5
Progressive Disclosure	A ~55-line simple skill with no bundle files and no content that belongs in a separate file; sections (Problem, Format, Slug, Examples, Workflow) are well-organized and easy to navigate, matching the simple-skill exception in the rubric notes. Not a 4 because there are no organization gaps or misplacement issues.	5 / 5
	Total	19 / 20 Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states a single concrete capability and provides unusually rich, natural trigger coverage including git command synonyms and vague-name examples. The only deduction is the second-person phrasing in the trigger clause, which the guidelines penalize on specificity.

Dimension	Reasoning	Score
Specificity	The description names one concrete action — 'Generate descriptive git branch names that follow the project's naming convention' — which is specific and complete for this single-purpose skill (base 4), but the trigger clause uses second person ('when you're about to run `git checkout -b`'), which the judging guidelines penalize by one point. It is not a 2 because the action named is concrete rather than generic.	3 / 5
Completeness	Explicitly answers both what ('Generate descriptive git branch names that follow the project's naming convention') and when ('Use this skill whenever the user asks to create a branch...') with concrete trigger phrases. Not a 4 because the when-clause enumerates specific natural triggers rather than being merely adequate.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including 'create a branch', 'name a branch', 'checkout a new branch', 'start working on a feature or fix', plus command synonyms 'git checkout -b' and 'git switch -c', and even vague-name patterns like 'fix/auth' and 'feature/billing'.	5 / 5
Distinctiveness Conflict Risk	Clear niche (branch naming) with distinct triggers tied to specific git commands and vague-branch-name patterns; minimal conflict risk with other skills. Not a 4 because no closely related skill would plausibly trigger on these phrases.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: akash-network/console
Path: .claude/skills/branch-namer/SKILL.md
Commit: 45693e5

Reviewed: 6 minutes ago

Table of Contents

Discovery Implementation Validation

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.