sqlitecpp-troubleshooting

Diagnose SQLiteCpp build, linker, compiler, and sqlite3 integration issues.

Quality

70%

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

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.

The body is a lean, well-organized error catalog with genuinely useful concrete fixes (CMake flags, package names, exact error signatures). Its main gaps are a few remedies stated as causes rather than commands and the absence of a verification step after applying a fix.

Dimension	Reasoning	Score
Conciseness	Every line maps a concrete symptom to a cause and fix with zero padding; no background on what SQLite or SQLiteCpp is, no filler, and no explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete, executable specifics are given throughout ("-DSQLITECPP_INTERNAL_SQLITE=ON", "libsqlite3-dev", "SQLITE_ENABLE_COLUMN_METADATA", exact error codes and symbol names), but a few entries stop at diagnosis ("Missing SQLiteCpp library or missing source file in build", "Rebuild sqlite3 with that flag") without the actual command to run.	4 / 5
Workflow Clarity	Each section unambiguously pairs an error message with its cause and remedies, but there is no diagnostic ordering (e.g., first classify compiler vs. linker error) and no step verifying the fix resolved the issue. No destructive/batch operation is involved, so the validation cap does not apply.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references, and is organized into clear per-error-type sections; per the rubric's simple-skill guideline this merits a 5.	5 / 5
	Total	18 / 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 clearly identifies a niche domain and what the skill does, but lacks any 'when to use' trigger guidance and natural user-side phrasing, which limits both completeness and trigger discoverability. It is concise and distinct, but reads as a capability label rather than a complete trigger description.

Suggestions

Add an explicit trigger clause, e.g. "Use when a SQLiteCpp build fails, or when you see linker errors like LNK2019 or 'undefined reference to sqlite3_xxx' while compiling against SQLiteCpp."

Include natural error-message keywords users would paste verbatim (LNK2019, 'undefined reference', 'error C2065', 'no member named') to improve trigger matching.

State the outcome, not just the activity: mention that the skill resolves/fixes these issues (which CMake flag or package to use), not merely 'diagnoses' them.

Dimension	Reasoning	Score
Specificity	Names the SQLiteCpp domain and four concrete issue areas ("build, linker, compiler, and sqlite3 integration") but the only action offered is "Diagnose", so coverage of what the skill actually does is not comprehensive.	3 / 5
Completeness	The 'what' is clear ("Diagnose SQLiteCpp build, linker, compiler, and sqlite3 integration issues") but there is no 'Use when...' or equivalent trigger clause; the judging guideline caps completeness at 3 for a missing explicit trigger.	3 / 5
Trigger Term Quality	"SQLiteCpp", "build", "linker", "compiler", and "sqlite3" are relevant keywords, but the natural phrases users would say when hitting these problems ("build fails", "undefined reference", "LNK2019", "won't compile") are missing, so common variations are absent.	3 / 5
Distinctiveness Conflict Risk	The named library "SQLiteCpp" establishes a clear niche with minimal conflict risk, though generic terms like "build" and "linker" leave minor overlap with general C++/CMake build troubleshooting skills.	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-troubleshooting/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.