sqlitecpp-build-cmake

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

Quality

86%

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 content is a tight, fully executable build reference with clear sequencing and well-organized sections that needs no external bundle. It exemplifies token-efficient, actionable skill writing.

Dimension	Reasoning	Score
Conciseness	The body is lean command-and-option lists with no explanation of what CMake or SQLite is; every line earns its place and assumes Claude's competence.	5 / 5
Actionability	Copy-paste ready commands for Windows and Unix, concrete CMake option flags with defaults, and specific ctest invocations fully cover the common build cases.	5 / 5
Workflow Clarity	Build steps are clearly sequenced (mkdir, cd, cmake, cmake --build) and the skill is single-purpose with no destructive/batch operations, so the simple-skill exception supports a top score.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references, it is organized into clear sections (Quick builds, Build scripts, Common options, Tests, Notes), satisfying the well-organized-sections criterion for a top score.	5 / 5
	Total	20 / 20 Passed

Description

73%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, third-person, and clearly pairs a what with a when clause scoped to a distinct niche. It is strong overall, held back only by moderate action specificity and trigger concreteness.

Suggestions

List a few more concrete build actions (e.g., configure, build targets, run ctest, toggle sanitizers) to raise specificity.

Add natural synonyms or extension-based triggers (e.g., CMakeLists, .cmake, CTest, ASAN builds) to broaden trigger coverage.

Tighten the "Use for" clause with more concrete triggers (e.g., "Use when building or testing SQLiteCpp, toggling its CMake options, or running ctest").

Dimension	Reasoning	Score
Specificity	"Build SQLiteCpp with CMake" names the domain and one concrete action, but does not enumerate several specific build actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action level 4.	3 / 5
Completeness	It gives a clear "what" (Build SQLiteCpp with CMake) and an explicit "Use for..." when-clause, but the trigger list is moderately specific rather than maximally concrete, placing it just below the level-5 anchor.	4 / 5
Trigger Term Quality	"CMake builds, tests, options, or build scripts" provides good natural keyword coverage a user would say, though it omits synonyms and file extensions, so it does not reach the comprehensive level 5.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to SQLiteCpp with CMake, it occupies a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 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-build-cmake/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.