CtrlK
BlogDocsLog inGet started
Tessl Logo

sqlitecpp-sqlite-flags

SQLiteCpp and sqlite3 feature flags for CMake and Meson builds.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

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.

An efficient, well-structured flag reference that delivers concrete, copy-paste-ready build options without padding, appropriately scoped for a simple single-purpose skill.

DimensionReasoningScore

Conciseness

A lean flag listing with one-line descriptions that assumes Claude's competence and adds no padding about what SQLite, CMake, or Meson are; every line earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready flag names with defaults (e.g. `SQLITECPP_INTERNAL_SQLITE` (ON)) and specific effects (e.g. `BUILD_SHARED_LIBS=ON` adds `SQLITECPP_COMPILE_DLL`), which is fully actionable guidance for a reference skill.

3 / 3

Workflow Clarity

A simple, single-purpose reference skill with clearly organized sections and no destructive or batch operations requiring validation checkpoints; per the simple-skills note this warrants a 3.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections by build system and category; per the guideline, simple skills of this size score 3 with well-organized sections, and no bundle files exist to verify further.

3 / 3

Total

12

/

12

Passed

Description

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

A concise, specific description that nails its niche and trigger terms, but it omits an explicit 'Use when...' guidance clause, leaving the activation context only implied and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when configuring, troubleshooting, or selecting SQLiteCpp/sqlite3 build options for CMake or Meson.'

Optionally surface one or two concrete actions (e.g. 'toggle sanitizers, coverage, codec, or column-metadata flags') to lift specificity toward 3.

DimensionReasoningScore

Specificity

Names the domain ("SQLiteCpp and sqlite3 feature flags") and scope ("for CMake and Meson builds") but does not list multiple concrete actions; closest to the anchor that names a domain and some actions without being comprehensive.

2 / 3

Completeness

Answers "what" (feature flags for CMake/Meson builds) but lacks an explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes the natural terms a developer would actually say — "SQLiteCpp", "sqlite3", "feature flags", "CMake", "Meson" — giving good coverage of the domain's trigger vocabulary.

3 / 3

Distinctiveness Conflict Risk

The description carves out a clear, narrow niche (SQLiteCpp/sqlite3 build-flag configuration) that is unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.