CtrlK
BlogDocsLog inGet started
Tessl Logo

sqlitecpp-coding-standards

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

60

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/sqlitecpp-coding-standards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is a compact, well-structured standards reference that assumes competence and gives concrete API and naming rules. Its main weakness is the absence of illustrative code examples and a short worked example showing the rules applied together.

DimensionReasoningScore

Conciseness

The body is lean, bullet-driven, and assumes Claude's competence; only the LF-line-endings bullet carries slightly more enforcement detail than strictly needed, keeping it just below a 5.

4 / 5

Actionability

It gives concrete, executable guidance (specific APIs like "tryExec()", exact naming prefixes, "#pragma once", "SQLITECPP_ASSERT()"), with only minor gaps such as no illustrative code snippets.

4 / 5

Workflow Clarity

As a single-purpose standards reference it is clearly organized into labeled sections that act as a checklist; it is not a multi-step workflow, but the single action (apply these rules when editing) is unambiguous with only minor sequencing/checkpoint gaps.

4 / 5

Progressive Disclosure

The body is under 50 lines with no external references needed and is organized into four well-labeled sections, meeting the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

17

/

20

Passed

Description

58%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 specific and clearly distinct to SQLiteCpp, but it omits any explicit "when to use" trigger guidance and relies on technical jargon rather than natural user phrases. Adding a "Use when..." clause with conversational triggers would lift completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when editing SQLiteCpp source, public headers, or writing Doxygen comments") to satisfy the 'when' half of completeness.

Include more natural trigger phrases a user might actually say (e.g., "SQLiteCpp style", "SQLiteCpp API", "Doxygen for SQLiteCpp") instead of only technical terms.

Optionally mention the file/scope triggers (e.g., "when touching core library or VariadicBind.h") to reduce overlap with generic C++ style skills.

DimensionReasoningScore

Specificity

The description names the domain ("SQLiteCpp coding standards") and several concrete categories ("core edits, public headers, style, and Doxygen"), listing multiple specific areas with only minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill covers but provides no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the missing-trigger guidance.

3 / 5

Trigger Term Quality

Relevant keywords ("SQLiteCpp", "coding standards", "Doxygen", "public headers") are present but skew toward technical jargon and lack the natural synonyms/variations a user would commonly say.

3 / 5

Distinctiveness Conflict Risk

The "SQLiteCpp" qualifier gives it a clear, narrow niche with minimal overlap risk, though the jargon-heavy triggers leave minor overlap potential with generic C++ style skills.

4 / 5

Total

14

/

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.

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.