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

88%

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

86%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.

A well-structured, highly actionable single-purpose skill body that earns its tokens with non-obvious project-specific detail (the release-trigger table) and concrete examples. The main improvement opportunity is adding an explicit validation step to the workflow.

Suggestions

Add an explicit validation step to the workflow (e.g., "Verify the slug is 3-6 kebab-case words and total length is under ~50 chars before suggesting") to create a validate-fix feedback loop and lift workflow_clarity to 5.

Trim the "The Problem" and Exception prose to the essential motivating point to push conciseness toward the lean anchor.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, with genuinely non-obvious project info (the CI/CD release-trigger table). It is not a 5 because the "The Problem" section and the Exception note explain motivation Claude could largely infer and could be trimmed.	4 / 5
Actionability	It provides a concrete format spec (`<type>/<scope>-<descriptive-slug>`), explicit slug principles (lead with a verb, drop articles, kebab-case, under ~50 chars), a 9-row before/after examples table, and a 6-step workflow — fully actionable, instruction-only guidance per the scoring notes.	5 / 5
Workflow Clarity	The 6-step workflow is clearly sequenced with a length-check (step 5) and a suggest-before-create checkpoint (step 6). It falls short of 5 because there is no explicit validation/feedback loop (e.g., verify the slug satisfies 3-6 words and length before suggesting).	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the body is well-organized into clearly headed sections (Problem, Format, Slug, Examples, Workflow) that are easy to navigate, satisfying the simple-skill exception for a self-contained single-purpose skill.	5 / 5
	Total	18 / 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 high-quality description that clearly states the skill's purpose and provides rich, natural trigger conditions including literal git commands. Its only real weakness is the use of second-person voice, which the rubric penalizes on specificity.

Suggestions

Rewrite in third person to avoid the second-person penalty: e.g., "Triggered when the user asks to create or name a branch, or when a vague branch name like `fix/auth` is detected."

Optionally surface 1-2 more concrete capabilities (e.g., "reads the project's .commitlintrc.json to pick valid scopes") to lift specificity toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	The description states one concrete action — "Generate descriptive git branch names that follow the project's naming convention" — which is specific but not comprehensive across several actions (anchor 3). It would score 4, but is reduced by 1 because the description uses second-person voice ("when you're about to run", "when you see a vague branch name").	3 / 5
Completeness	It explicitly answers both what ("Generate descriptive git branch names...") and when ("Use this skill whenever the user asks... Also trigger when you see a vague branch name..."), with concrete trigger phrases.	5 / 5
Trigger Term Quality	It comprehensively covers natural trigger phrases users would say ("create a branch", "name a branch", "start working on a feature or fix") plus the literal commands `git checkout -b` and `git switch -c`, matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (branch naming) with distinct triggers tied to branch-specific commands and vague branch-name detection, with minimal overlap risk against related commit-message skills.	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: a321fa4

Reviewed: about 14 hours 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.