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

—

Does it follow best practices?

Impact

93%

1.14x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

An exemplary instruction-only skill body: concrete, well-organized, project-specific where it matters, and free of padding or basic-concept exposition. No bundle files exist and none are needed.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a compact format spec, a project-specific CI/CD type table (non-obvious domain knowledge Claude would not know), slug principles, and an examples table. It does not explain basic concepts Claude already knows and nearly every token earns its place.	3 / 3
Actionability	Fully actionable: concrete format '<type>/<scope>-<descriptive-slug>', an explicit type table, a concrete scope source ('Read `.commitlintrc.json`'), slug writing rules, and a bad->good examples table give copy-paste-ready guidance.	3 / 3
Workflow Clarity	A clear six-step sequence (read commitlintrc -> determine type -> pick scope -> write slug -> check length -> suggest before creating) with a length-check checkpoint and a final 'suggest to the user before creating it' confirmation gate; appropriate for this single-task skill.	3 / 3
Progressive Disclosure	A single self-contained SKILL.md with no external bundle files (references/scripts/assets absent) and well-organized sections (Problem, Format, Slug, Examples, Workflow), satisfying the simple-skill allowance for scoring 3 without external references.	3 / 3
	Total	12 / 12 Passed

Description

90%

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, specific description with explicit triggers and a clear niche; the only weakness is second-person voice ('you're about to run', 'you see'), which the rubric penalizes on specificity.

Suggestions

Rewrite in third person to avoid the specificity penalty, e.g. 'Generate descriptive git branch names... Use this skill whenever the user asks to create or name a branch, starts a feature or fix, or is about to run `git checkout -b` / `git switch -c`. Also trigger when a vague branch name like `fix/auth` or `feature/billing` appears...'

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Generate descriptive git branch names that follow the project's naming convention'), but uses second-person voice ('when you're about to run', 'you see a vague branch name'), which per the rubric reduces the specificity score by one from a base of 3.	2 / 3
Completeness	Clearly answers both what ('Generate descriptive git branch names...') and when via an explicit 'Use this skill whenever...' clause plus a secondary 'Also trigger when...' condition.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'create a branch', 'name a branch', 'start working on a feature or fix', 'checkout a new branch', 'git checkout -b', 'git switch -c', plus vague-name cues like 'fix/auth' and 'feature/billing'.	3 / 3
Distinctiveness Conflict Risk	A clear, narrow niche (git branch naming) with distinct triggers tied to branch-creation commands, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 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
Commit: 7b6a52e

Reviewed: 1 day 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.