sqlitecpp-troubleshooting

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

Quality

79%

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

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 troubleshooting reference: concrete error strings mapped to specific, executable fixes with clear section organization and no unnecessary padding.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and token-efficient, with every line mapping a concrete error to a fix and no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	It pairs exact error strings (e.g. 'LNK2019 unresolved external symbol', 'undefined reference to sqlite3_column_origin_name') with directly executable fixes such as installing libsqlite3-dev and specific CMake flags like -DSQLITECPP_INTERNAL_SQLITE=ON.	5 / 5
Workflow Clarity	Content is clearly organized by error category with an unambiguous match-error-to-fix pattern, but it is a diagnostic reference catalog rather than a sequenced workflow with validation checkpoints.	4 / 5
Progressive Disclosure	As a short (<50 line) self-contained troubleshooting skill with well-organized section headers and no need for external references, it meets the simple-skill exception for a top progressive-disclosure score.	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 clearly targets a distinct niche, but it omits an explicit 'when to use' trigger clause and leans on a single diagnostic verb, which limits completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user reports SQLiteCpp build, linker, or compiler errors, or sqlite3 symbol/dependency issues.'

Broaden the action language beyond a single 'Diagnose' verb to describe distinct actions (e.g., 'identify missing includes, resolve linker symbols, enable internal sqlite3').

Include common synonyms a user might say (e.g., 'CMake', 'MSVC', 'undefined reference', 'unresolved external') to strengthen trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the SQLiteCpp domain and several concrete issue categories (build, linker, compiler, sqlite3 integration), but relies on a single action verb ('Diagnose') rather than listing multiple distinct actions, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	The 'what' is clear (diagnose SQLiteCpp build/linker/compiler/sqlite3 issues) but there is no 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Phrases like 'build, linker, compiler, and sqlite3 integration issues' are exactly what a user debugging SQLiteCpp would say, giving good keyword coverage with only minor synonyms/extensions missing.	4 / 5
Distinctiveness Conflict Risk	The narrow SQLiteCpp niche with distinct, specific triggers (build/linker/compiler/sqlite3 integration) makes overlap with other skills minimal.	5 / 5
	Total	15 / 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: 672a1e0

Reviewed: 5 days 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.