CtrlK
BlogDocsLog inGet started
Tessl Logo

sqlitecpp-update-sqlite

How to update the bundled SQLite3 amalgamation (sqlite3/sqlite3.c and sqlite3.h), the Meson wrap, README.md, and CHANGELOG.md. Use when upgrading SQLite, refreshing the vendored amalgamation, or bumping the sqlite3 wrap.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-sequenced upgrade runbook that respects token budget and delegates detail appropriately. The two soft spots are the Meson wrap step, which under-specifies where the new source_hash comes from, and the absence of any failure-handling guidance around the build-and-test checkpoint.

Suggestions

In the Meson wrap step, state where the new source_hash comes from (e.g. the wrapdb release page or `meson wrap update`), so the bump is fully executable rather than naming fields alone.

Add a short failure path after step 6: what to check if the CMake or Meson build/tests fail against the new amalgamation (e.g. flag drift, feature-define changes).

DimensionReasoningScore

Conciseness

The ~45-line body stays lean and assumes competence: no explanation of what SQLite or Meson is, and every sentence carries repo-specific facts (dual CMake/Meson builds, version-to-filename encoding, copyright year conventions). Matches the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete guidance throughout: exact file paths, a worked version-encoding example (3.51.3 = 3510300), a verbatim README line format, and a CHANGELOG line template. Falls short of fully executable because the wrap step names the fields to bump but not where to obtain the new source_hash, and no commands are given for extraction or verification.

4 / 5

Workflow Clarity

A clear numbered 1-6 sequence with an explicit validation checkpoint ("Build and run the tests on both CMake and Meson"), but there is no feedback loop for what to do when tests fail or the hash mismatches. Matches 'clear sequence with most checkpoints present; minor validation gaps' rather than the 5 anchor's explicit error-recovery loops.

4 / 5

Progressive Disclosure

No bundle files exist; the body is under 50 lines with well-organized sections, and all detail that would bloat it (build steps, flag list, workflow conventions, release process) is delegated via clearly-signaled one-level [[...]] links to other skills. Satisfies the simple-skill exception for a full score.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description: it names every artifact the skill touches, uses an explicit 'Use when...' clause with natural trigger phrases, and occupies a distinct niche. The only weakness is mild synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

"How to update the bundled SQLite3 amalgamation (sqlite3/sqlite3.c and sqlite3.h), the Meson wrap, README.md, and CHANGELOG.md" lists multiple concrete artifacts and actions with comprehensive coverage for this domain, in third-person voice. The 4 anchor requires 'minor gaps in coverage', but every deliverable of the task is enumerated.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' enumerates the amalgamation, wrap, README, and CHANGELOG updates, and an explicit 'Use when...' clause gives three concrete trigger phrases. Matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

"Use when upgrading SQLite, refreshing the vendored amalgamation, or bumping the sqlite3 wrap" provides natural trigger phrasing, but a few common variations are missing (e.g. "update SQLite", "SQLite version", file extensions). Good coverage, just shy of the comprehensive-synonyms 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"bundled SQLite3 amalgamation" and "Meson wrap" define a clear niche with distinct triggers unlikely to fire for other skills. Not the 4 anchor, which requires minor overlap risk with closely related skills.

5 / 5

Total

19

/

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.

Validation — 16 / 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.