sqlitecpp-git-branching

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

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/sqlitecpp-git-branching/SKILL.md

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.

The content is a tight, well-structured instruction skill with concrete patterns and a clear workflow. Including the actual branch-creation command and an explicit post-creation verification step would round out actionability and workflow clarity.

Suggestions

Add the literal branch-creation command (e.g. `git checkout -b <branch-name> master`) so guidance is copy-paste ready.

Add an explicit verification checkpoint after branch creation (e.g. re-run `git status` to confirm the new branch).

Clarify what counts as a valid `<type>` (fix/feature/etc.) so the naming pattern is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no padding, no explanation of git concepts, every line carries actionable information.	5 / 5
Actionability	Provides concrete, executable commands (`git status`) and concrete branch-name patterns with examples, but the branch-creation command itself is not given verbatim.	4 / 5
Workflow Clarity	Sequenced steps with an explicit `git status` checkpoint and guidance for the accidental-edit-on-master case; minor gap is the absence of an explicit validation/verify step after branch creation.	4 / 5
Progressive Disclosure	A short, single-purpose skill under 50 lines with well-organized sections and no external bundle files needed, so the simple-skill exception applies and structure is clean.	5 / 5
	Total	18 / 20 Passed

Description

61%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 and names a clear, distinct niche with natural trigger terms, but it lacks an explicit 'when to use' clause and only lightly enumerates concrete actions. Adding a 'Use when...' trigger phrase would raise completeness and trigger coverage.

Suggestions

Add an explicit 'Use when ...' clause naming the trigger situations (e.g. 'Use when starting a task, issue, or feature on the SQLiteCpp repo').

List a couple more concrete actions to strengthen specificity (e.g. naming convention enforcement and maintenance/release branch patterns).

Include common synonyms or issue-number phrasing to broaden natural trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('SQLiteCpp branch naming and creation rules') with concrete actions (naming, creation), but coverage is minimal and generic rather than listing multiple specific actions.	3 / 5
Completeness	States a clear 'what' (branch naming and creation rules) but the 'when' is only weakly implied rather than an explicit 'Use when...' clause, so per the guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural user-facing phrases ('starting tasks, issues, or features') that a user would plausibly say, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to SQLiteCpp-specific branch conventions, making it distinct with only minor overlap risk against generic git-branching skills.	4 / 5
	Total	14 / 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: 672a1e0

Reviewed: 5 days 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.