sqlitecpp-testing-practices

GoogleTest patterns and testing practices for SQLiteCpp test coverage and structure.

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-testing-practices/SKILL.md

Quality

Content

93%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 body is an exemplary lean, actionable skill: concrete code style, exact build registration targets, and runnable test commands with no wasted tokens. The only gap is a missing explicit verification step in the add-a-test workflow.

Dimension	Reasoning	Score
Conciseness	Every section delivers only repo-specific, non-obvious facts (AAA comment style, ':memory:' preference, TEST() vs TEST_F() guidance, exact registration variables) with zero padding or explanation of concepts Claude already knows — matches the 'lean and efficient' anchor.	5 / 5
Actionability	The skill provides copy-paste-ready commands (ctest, gtest_filter invocations, meson test) and exact registration targets (SQLITECPP_TESTS in CMakeLists.txt, sqlitecpp_test_srcs in meson.build), covering the common cases fully.	5 / 5
Workflow Clarity	The add-a-test flow (create tests/NewClass_test.cpp, register in CMake, register in meson) is a clear sequence and running commands exist, but there is no explicit checkpoint telling the reader to run/verify the new test after registration — fits 'clear sequence with most checkpoints present; minor validation gaps' rather than the explicit-validation anchor.	4 / 5
Progressive Disclosure	The skill is under 60 lines with no bundle files and no need for external references; its well-organized sections, canonical project-file references, and cross-references to sibling skills satisfy the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

53%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 specific and distinct thanks to the GoogleTest/SQLiteCpp pairing, but it lacks any 'Use when...' trigger guidance and omits natural synonyms users would say. Adding an explicit trigger clause and concrete actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or modifying tests for SQLiteCpp, adding new *_test.cpp files, or running the GoogleTest suite.'

Include natural synonyms users would actually say, such as 'unit tests', 'gtest', and 'add a test for ...', to improve trigger term coverage.

List the concrete actions the skill covers (create test files, register them in CMakeLists.txt and meson.build, run tests via ctest/meson test) to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('GoogleTest patterns and testing practices') and 1-2 actions ('test coverage and structure') but does not list several concrete actions such as writing new test files or registering them in build files, matching the anchor for domain plus 1-2 actions rather than the level above.	3 / 5
Completeness	It has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	'GoogleTest', 'SQLiteCpp', and 'test coverage' are relevant keywords, but common natural phrases a user would say ('add a unit test', 'run the tests', 'gtest') are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'for SQLiteCpp test coverage and structure' carves a clear niche distinct from the sibling build/workflow skills, though 'testing practices' remains broad enough to slightly overlap generic testing skills, fitting the 'mostly distinct' anchor.	4 / 5
	Total	13 / 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-testing-practices/SKILL.md
Commit: 6f9326a

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