sqlitecpp-git-branching

SQLiteCpp branch naming and creation rules for starting tasks, issues, or features.

Quality

81%

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

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.

The body is an exemplary compact instruction-only skill: lean, fully actionable naming rules with worked examples, an explicit pre-edit checkpoint and recovery path for accidental master edits, and well-organized sections that need no external files. The only minor improvement would be including the actual branch-creation command.

Dimension	Reasoning	Score
Conciseness	The body is 37 lean lines with zero git-concept explanation; every rule carries information Claude does not already know (e.g. "Issue ID is optional; do not use a `000-` prefix"). Version strings appear only as clearly-marked examples ("e.g. `update-sqlite-3.52.2`"), so no time-sensitivity penalty applies.	5 / 5
Actionability	Concrete executable guidance throughout: the `git status` command, copy-paste-ready naming templates with worked examples (`123-fix-short-description`), and explicit handling of edge cases (accidental edits on master, branch-only requests). The actual branch-creation command (`git checkout -b`) is not given, which is a minor gap keeping it below fully copy-paste-ready.	4 / 5
Workflow Clarity	The sequence is unambiguous with a checkpoint (run `git status` before acting), an explicit error-recovery path ("If edits were accidentally made on `master`, create the task branch with the working tree intact"), and a clear stop condition for branch-only requests. Branch creation is not destructive or batch, so no validation cap applies, and the simple-skill exception holds.	5 / 5
Progressive Disclosure	The skill is under 50 lines, self-contained with no bundle files (no references/, scripts/, or assets/ exist), and organized into clear single-purpose sections (When to create a branch, Before starting work, Branch naming, Maintenance branch conventions, Branch-only requests). Per the rubric, well-organized sections suffice for a small skill with no external references needed.	5 / 5
	Total	19 / 20 Passed

Description

70%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 concise, concrete, and clearly scoped to a niche (SQLiteCpp branching), with a serviceable when-clause. Its main weaknesses are limited coverage of what the skill actually handles (maintenance-branch naming is absent from the description) and trigger phrasing that could be more explicit.

Suggestions

Rewrite the when-clause as explicit trigger guidance, e.g. "Use when the user starts a new task, feature, or issue, references a GitHub issue number, or asks to create a git branch in the SQLiteCpp repo."

Broaden the what to reflect the skill's actual coverage: mention maintenance branch naming (update-sqlite-X.Y.Z, release-X.Y.Z, minor-line branches) alongside task-branch naming.

Include natural trigger keywords users would actually say — "git branch", "new branch", "branch name", "checkout" — to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("SQLiteCpp branch naming and creation rules") and two concrete actions (naming, creation), matching the 'names domain and 1-2 concrete actions' anchor. It omits the maintenance-branch coverage the body actually provides (update-sqlite, release, minor-line branches), so it is not comprehensive enough for a 4.	3 / 5
Completeness	Both what ("branch naming and creation rules") and when ("for starting tasks, issues, or features") are present, matching anchor 4. The when-clause is explicitly stated rather than merely implied (so above anchor 3), but it is not phrased as concrete trigger guidance ("Use when the user mentions..."), so it does not reach 5.	4 / 5
Trigger Term Quality	"branch", "task", "issue", and "feature" are natural terms users would say when needing this skill, giving good keyword coverage. Common variations like "git", "new branch", or "start working on" are missing, so it falls short of the comprehensive-synonyms anchor at 5.	4 / 5
Distinctiveness Conflict Risk	Naming "SQLiteCpp" establishes a clear niche with minimal generic conflict risk. However, sibling skills ([[sqlitecpp-update-sqlite]], [[sqlitecpp-release]]) also govern branch names (update-sqlite-X.Y.Z, release-X.Y.Z), creating minor overlap that the description does not distinguish.	4 / 5
	Total	15 / 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: SRombauts/SQLiteCpp
Path: .claude/skills/sqlitecpp-git-branching/SKILL.md
Commit: 6f9326a

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.