CtrlK
BlogDocsLog inGet started
Tessl Logo

sqlitecpp-sqlite-flags

SQLiteCpp and sqlite3 feature flags for CMake and Meson builds.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/sqlitecpp-sqlite-flags/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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, well-structured reference catalog that respects token budget and is easy to navigate; its only gap is the absence of an example command showing how to apply the flags.

Suggestions

Add one short example showing how to pass a flag, e.g. a CMake `-DSQLITECPP_USE_ASAN=ON` or Meson `-Dsqlitecpp_use_asan=true` invocation.

Clarify the CMake-vs-Meson default divergence for column metadata in a single consolidated note rather than inline parentheticals.

DimensionReasoningScore

Conciseness

The body is a lean bullet catalog of flags with one-line purposes and defaults; it assumes Claude's competence and explains no background concepts, so every token earns its place.

5 / 5

Actionability

Each flag is named with its default and effect, giving concrete reference guidance, but no example build invocation (e.g. a CMake -D or Meson -D command) is shown, leaving a minor gap.

4 / 5

Workflow Clarity

This is a simple single-purpose reference skill under 50 lines with well-organized sections and no multi-step or destructive process, so the simple-skill exception applies and the single lookup action is unambiguous.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clearly labeled sections by build system and category, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

65%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 and targets a clear, low-conflict niche, but it omits explicit usage triggers and frames the skill as a topic rather than enumerating concrete actions.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when configuring SQLiteCpp or sqlite3 build options for CMake or Meson.'

List 1-2 concrete actions (e.g. 'configure', 'enable/disable') to lift specificity above a topic label.

Include common synonyms such as 'build options' or 'compile flags' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names a concrete domain ('SQLiteCpp and sqlite3 feature flags for CMake and Meson builds') with specific build systems, but lists no discrete actions; it is a topic label rather than an action inventory, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear (feature flags for CMake/Meson builds), but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces the exact technical terms a developer would say ('SQLiteCpp', 'sqlite3', 'feature flags', 'CMake', 'Meson'), giving good keyword coverage, though natural synonyms like 'build options' or 'compile flags' are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and unambiguous (SQLiteCpp + sqlite3 build flags for CMake/Meson), making conflict with other skills minimal and triggers distinct.

5 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
SRombauts/SQLiteCpp
Reviewed

Table of Contents

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.