CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/sqlite-node-best-practices

SQLite best practices for Node.js with better-sqlite3 — WAL mode, pragmas, foreign keys, STRICT tables, transactions, migrations, graceful shutdown, and query patterns

97

1.65x
Quality

98%

Does it follow best practices?

Impact

96%

1.65x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides comprehensive specificity with concrete technical concepts, includes natural trigger terms users would actually search for, explicitly states both capabilities and usage scenarios, and carves out a distinct niche that won't conflict with general database or Node.js skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: WAL mode, pragma configuration, foreign keys, transactions, migrations, STRICT tables, prepared statements, graceful shutdown, and performance patterns. These are all concrete, actionable technical elements.

3 / 3

Completeness

Clearly answers both what (SQLite best practices covering WAL mode, pragmas, transactions, etc.) AND when with explicit 'Use when...' clause listing five specific trigger scenarios including building/reviewing apps, seeing imports, setup, debugging, and migrating.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'Node.js', 'SQLite', 'better-sqlite3', 'database', 'slow queries', 'SQLITE_BUSY errors', 'migrations', 'in-memory storage'. These match real user vocabulary when seeking help with SQLite in Node.js.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche: specifically targets Node.js + better-sqlite3 combination, mentions library-specific imports, and includes unique triggers like 'SQLITE_BUSY errors' that wouldn't apply to other database skills or general Node.js skills.

3 / 3

Total

12

/

12

Passed

Implementation

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an exemplary skill document that provides comprehensive, production-ready SQLite guidance for Node.js. It excels at being both thorough and concise, with executable code examples, clear explanations of why each configuration matters, and practical patterns for common scenarios. The checklist and verifier references provide excellent validation checkpoints.

DimensionReasoningScore

Conciseness

The content is dense with actionable information and avoids explaining basic concepts Claude would know. Every section provides specific, necessary configuration details without padding or unnecessary context.

3 / 3

Actionability

Provides fully executable TypeScript/SQL code throughout, with copy-paste ready examples for connection setup, migrations, transactions, and prepared statements. Includes specific pragma values, not just descriptions.

3 / 3

Workflow Clarity

Clear sequencing throughout: pragmas before queries, migrations in order, transactions with automatic rollback explained. The migration pattern includes explicit transaction wrapping for safety, and the checklist provides validation checkpoints.

3 / 3

Progressive Disclosure

Well-organized with clear section headers, a summary checklist at the end, and references to external verifier files. Content is appropriately structured for a comprehensive skill without unnecessary nesting or monolithic walls of text.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (538 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Reviewed

Table of Contents