sqlitecpp-coding-standards

SQLiteCpp coding standards and API rules for core edits, public headers, style, and Doxygen.

Quality

72%

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

Quality

Content

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

The body is an exceptionally lean, concrete coding-standards reference that assumes Claude's competence and cites specific symbols. Its only gap is the absence of a sequenced application workflow with validation checkpoints, which keeps workflow clarity at 2.

Suggestions

Add a short 'Before submitting a core edit' checklist that sequences the rules (e.g., verify RAII, then header hygiene, then Doxygen, then style) to give the rules an application order.

Include a one-line verification step such as running the repo's style/lint check or grep for sqlite3.h includes in public headers.

Optionally split the naming-convention table into a reference file if the standards grow, keeping SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	The body is a lean bullet list of rules with no concept explanations (it assumes Claude knows RAII, Allman braces, etc.), so every token earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Rules cite concrete symbols and commands ('SQLITECPP_ASSERT()', 'tryExec()', '#pragma once', 'm'/'a'/'b' prefixes), giving specific actionable guidance; per scoring notes, absence of code in an instruction-only skill is not penalized when guidance is this concrete.	3 / 3
Workflow Clarity	Content is well organized into categories but is a flat reference checklist with no sequenced workflow or validation checkpoints, fitting 'sequence present but checkpoints missing or implicit' rather than the 'clear sequence with explicit validation' anchor.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no external references needed and is organized into clear signed sections (Non-negotiables, Error handling, Documentation and style, Naming conventions), matching the simple-skill allowance for a top score on organization alone.	3 / 3
	Total	11 / 12 Passed

Description

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

The description is specific and distinctive within the SQLiteCpp niche, but it only states what the skill covers without any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when editing SQLiteCpp core code, public headers, or writing Doxygen comments.'

Lead with concrete actions ('Enforce RAII, check public headers exclude sqlite3.h, format Doxygen') instead of listing topic categories.

Add common user phrasings like 'SQLiteCpp style' or 'SQLiteCpp API rules' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('SQLiteCpp coding standards') and several sub-areas ('core edits, public headers, style, and Doxygen'), but lists categories rather than concrete actions, matching the 'names domain and some actions' anchor rather than the 'multiple specific concrete actions' anchor.	2 / 3
Completeness	It states what the skill covers but provides no 'Use when...' clause or equivalent trigger guidance, so per the guidelines completeness is capped at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	Terms like 'SQLiteCpp', 'coding standards', 'public headers', and 'Doxygen' are relevant, but coverage of natural user phrasings is partial and there is no explicit trigger guidance, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The narrow 'SQLiteCpp coding standards' niche with library-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 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-coding-standards/SKILL.md
Commit: 736fb31

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