branches

Create and name git branches following project conventions. Use when creating branches, checking out new branches, or the user mentions branch naming.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The body is a tight, actionable reference: a clear pattern, concrete examples, a type catalog, and issue-reference rules, with no superfluous explanation. It is well structured for a simple single-purpose skill.

Dimension	Reasoning	Score
Conciseness	Lean, well-organized reference with no padding or explanation of concepts Claude already knows; every line (pattern, examples, type list, issue refs) earns its place.	5 / 5
Actionability	Provides a concrete copy-paste pattern '<type>/<issue-ref>/<short-title>' plus many specific real examples covering internal, open-source, and special-case branches.	5 / 5
Workflow Clarity	A simple single-purpose naming skill where the single action is unambiguous via a clear pattern and examples; the simple-skill exception applies and no destructive/batch validation cap is relevant.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections (Branch Types, Issue References), satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	20 / 20 Passed

Description

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

The description is third-person, concise, and clearly answers both what the skill does and when to invoke it, with natural trigger phrases. Its main limitation is modest capability specificity (only create/name actions).

Suggestions

Consider adding a third concrete action or clarifying that the skill also covers validating/updating branch names against conventions, to lift specificity above the 1-2 actions anchor.

Add 'checkout' as an explicit standalone trigger synonym and possibly 'git branch' to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (git branches) and two concrete actions ('Create and name ... branches following project conventions'), matching the 1-2 concrete actions anchor; not below 2 because actions are concrete, not above 3 because coverage is limited to create/name with no further capabilities.	3 / 5
Completeness	Explicitly answers what ('Create and name git branches following project conventions') and when ('Use when creating branches, checking out new branches, or the user mentions branch naming') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing phrases like 'creating branches', 'checking out new branches', and 'branch naming' are present; not 5 because it lacks synonyms/variants beyond these and omits the term 'checkout' as a standalone verb.	4 / 5
Distinctiveness Conflict Risk	Branch naming is a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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: redis/RedisInsight
Path: .ai/skills/branches/SKILL.md
Commit: 6029714

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.