Conciseness

The body is command-first and lean — quick builds, script descriptions, a compact options table, and test commands with no concept explanations Claude already knows. Not 5 because the Notes section carries a few prose lines (the CMake policy explanation and version-maintenance guidance) that could be trimmed.

Actionability

Fully executable, copy-paste-ready commands for both Windows and Unix ('cmake -G "Visual Studio 18 2026" -DSQLITECPP_BUILD_TESTS=ON ...', 'cmake --build .', 'ctest --output-on-failure'), plus a complete options table with default values. The common cases (build with tests/examples, run tests, filter tests) are all covered.

Workflow Clarity

The quick-build sections give an unambiguous configure→build sequence and the Tests section supplies ctest commands with failure output as a feedback mechanism. Not 5 because the build→test chaining is implicit across sections rather than one stated flow with an explicit verify step; not 3 because sequences are concrete and complete.

Progressive Disclosure

The skill is under 50 lines, has no external references and needs none (no references/, scripts/, or assets/ directories exist), and is organized into clear, well-labeled sections (Quick builds, Build scripts, Common options, Tests, Notes). This meets the simple-skill exception: well-organized sections alone warrant a 5.

Specificity

"Build SQLiteCpp with CMake" names the exact domain and one concrete action, but does not list several specific actions (e.g., configure, build, run tests, set options) in the what-statement. It matches 'names domain and 1-2 concrete actions, but not comprehensive' better than anchor 4, which expects several listed actions.

Completeness

Explicit 'what' ("Build SQLiteCpp with CMake") and explicit 'when' ("Use for CMake builds, tests, options, or build scripts") are both present, so no cap applies. Not 5 because the what is a single terse action and the when-clause could be more concrete (e.g., 'when the user asks to compile, test, or configure SQLiteCpp').

Trigger Term Quality

"CMake builds, tests, options, or build scripts" are natural phrases a user would say when needing this skill. Not 5 because common synonyms such as 'compile', 'configure', or 'run tests' are missing; not 3 because coverage is good, not just 'some relevant keywords'.

Distinctiveness Conflict Risk

"Build SQLiteCpp with CMake" carves out a clear niche — a specific named library plus a specific build system — so it is unlikely to trigger for unrelated skills. Re-reading anchor 4 ('minor overlap risk with closely related skills') does not fit better; only a generic CMake-build skill for other libraries could overlap, and the project name prevents that.