sqlitecpp-build-cmake

Build SQLiteCpp with CMake. Use for CMake builds, tests, options, or build scripts.

Quality

95%

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-3

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, fully actionable CMake build reference with executable commands, well-organized sections, and an implicit verification path via ctest. It models conciseness and actionability well for a simple build skill.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-pointed guidance with no filler and no explanation of what CMake or SQLite is; every token earns its place and it assumes Claude's competence.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands (e.g. `cmake -G "Visual Studio 18 2026" -DSQLITECPP_BUILD_TESTS=ON ..`, `cmake --build .`, `ctest --output-on-failure`) with concrete option names and defaults.	3 / 3
Workflow Clarity	For a simple single-purpose build skill the sequence is unambiguous (mkdir build → configure → build) and the dedicated Tests section with ctest serves as the verification step, satisfying the simple-skill allowance.	3 / 3
Progressive Disclosure	The skill is under 50 lines with no external bundle files needed and is organized into clearly labeled sections (Quick builds, Build scripts, Common options, Tests, Notes), meeting the level-3 simple-skill bar.	3 / 3
	Total	12 / 12 Passed

Description

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

The description is concise and clearly answers both what the skill does and when to use it, with an explicit trigger clause and a distinct niche. Its only weakness is that the capability statement is a single action rather than a fuller enumeration of concrete build/test capabilities.

Suggestions

Expand the capability clause to list concrete actions, e.g. "Configure, build, test, and lint SQLiteCpp with CMake."

Consider adding a natural trigger phrasing like "when the user needs to build or run SQLiteCpp tests" to broaden real-world term coverage.

Dimension	Reasoning	Score
Specificity	"Build SQLiteCpp with CMake" names the domain and a concrete action, and "tests, options, or build scripts" enumerates trigger contexts, but it does not list multiple distinct concrete capabilities (e.g. configure, build, test, run lint) the way the level-3 anchor does.	2 / 3
Completeness	It states what the skill does ("Build SQLiteCpp with CMake") and provides an explicit "Use for ..." trigger clause answering when to use it, satisfying the level-3 anchor for both what and when.	3 / 3
Trigger Term Quality	"Use for CMake builds, tests, options, or build scripts" gives natural, varied terms a user would actually say when needing this skill, matching the level-3 anchor's coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The pairing of "SQLiteCpp" with "CMake" creates a clear niche with distinct triggers unlikely to collide with unrelated skills.	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: SRombauts/SQLiteCpp
Path: .claude/skills/sqlitecpp-build-cmake/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.