sqlitecpp-workflow

SQLiteCpp change workflow checklists for API, tests, build files, and CHANGELOG updates. Use when adding a method or class, editing build files, or writing a CHANGELOG entry for a PR.

Quality

93%

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

87%Weight 40%Scale 1-3

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

A tight, highly actionable workflow skill with concrete paths, commands, and formats; its only gap is the absence of explicit build/test validation checkpoints and error-recovery feedback loops in the numbered workflows.

Suggestions

Add an explicit validation step to the 'Add a method' and 'Add a class' workflows (e.g., 'Build and run tests: verify the suite passes before committing') so each sequence includes a concrete verification checkpoint.

Include a short feedback loop for failure (e.g., 'If tests fail, fix the issue and re-run before pushing') to satisfy the error-recovery expectation for commit/push workflows.

State the CHANGELOG-separate-commit rule once in the CHANGELOG conventions section and reference it from the checklists/git sections to reduce the redundancy across four places.

Dimension	Reasoning	Score
Conciseness	Lean, action-focused checklists and numbered steps with no explanation of concepts Claude already knows (no 'what is CMake' padding); every section earns its place, though the CHANGELOG-separate-commit rule is restated across a few sections for checklist self-containment.	3 / 3
Actionability	Gives concrete, executable specifics: exact paths ('include/SQLiteCpp/<Class>.h', 'src/<Class>.cpp'), build variables ('SQLITECPP_SRC', 'SQLITECPP_INC'), commands ('gh pr create'), Doxygen tags, and a precise CHANGELOG line format ('- <description> (#NNN)').	3 / 3
Workflow Clarity	Add-a-method/Add-a-class sequences are clearly numbered with a checklist and an explicit ask-permission checkpoint before pushing, but there is no explicit build/test validation step in the workflows and no error-recovery feedback loop (what to do if tests fail), capping it below the top anchor.	2 / 3
Progressive Disclosure	A single-file skill with no bundle files (references/scripts/assets empty) and no need for them; content is well-organized into clearly headed sections, and the only cross-references ([[sqlitecpp-release]], [[sqlitecpp-update-sqlite]], humanizer) are one-level and clearly signaled.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person description that clearly states both the capability and explicit use-when triggers, narrowly scoped to SQLiteCpp with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete categories - 'API, tests, build files, and CHANGELOG updates' - rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('checklists for API, tests, build files, and CHANGELOG updates') and when ('Use when adding a method or class...'), matching the top anchor with an explicit 'Use when' trigger.	3 / 3
Trigger Term Quality	'adding a method or class, editing build files, or writing a CHANGELOG entry for a PR' are natural terms a SQLiteCpp contributor would actually say, giving good coverage rather than just jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to 'SQLiteCpp change workflow', a clear niche unlikely to trigger for unrelated skills; not generic enough to conflict.	3 / 3
	Total	12 / 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: SRombauts/SQLiteCpp
Path: .claude/skills/sqlitecpp-workflow/SKILL.md
Commit: 736fb31

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