sqlite-ops
Patterns for SQLite databases in Python projects - state management, caching, and async operations. Triggers on: sqlite, sqlite3, aiosqlite, local database, database schema, migration, wal mode.
87
80%
Does it follow best practices?
Impact
100%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/sqlite-ops/SKILL.mdQuality
Discovery
72%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 establishes a clear niche around SQLite in Python and provides good trigger terms covering library names and key concepts. However, it would benefit from listing more concrete actions (e.g., 'create schemas', 'write migrations', 'configure connection pooling') and converting the trigger list into a more explicit 'Use when...' clause that describes user scenarios.
Suggestions
Replace the category-level terms ('state management, caching, async operations') with specific concrete actions like 'design database schemas, write migrations, configure WAL mode, implement async queries with aiosqlite'.
Add an explicit 'Use when...' clause describing scenarios, e.g., 'Use when the user needs to set up or query a local SQLite database in a Python project, write schema migrations, or configure async database access.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SQLite databases in Python) and mentions some areas (state management, caching, async operations), but these are more like categories than concrete actions. It doesn't list specific actions like 'create tables', 'write migrations', or 'configure WAL mode'. | 2 / 3 |
Completeness | The 'what' is partially addressed (patterns for SQLite in Python), and the 'Triggers on:' clause serves as a partial 'when' equivalent. However, there's no explicit 'Use when...' clause describing scenarios, and the trigger list alone doesn't fully articulate when to select this skill over others. | 2 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'sqlite', 'sqlite3', 'aiosqlite', 'local database', 'database schema', 'migration', 'wal mode'. These cover both library names and conceptual terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of SQLite + Python + specific libraries (aiosqlite, sqlite3) and concepts (WAL mode, migration) creates a clear niche that is unlikely to conflict with general database skills or other language-specific database skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that is concise, actionable, and well-structured. The code examples are executable and the reference structure follows best practices for progressive disclosure. The main weakness is the lack of explicit workflow sequencing and validation checkpoints for operations like initial database setup or schema changes, though for a reference-style skill this is a minor gap.
Suggestions
Consider adding a brief numbered workflow for common multi-step operations (e.g., 'Setting up a new database: 1. Create connection with WAL mode, 2. Create schema, 3. Verify with .tables, 4. Insert test data').
Add a validation step after enabling WAL mode (e.g., checking the return value of the PRAGMA) to demonstrate verification practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what SQLite is or how Python works. Tables are used efficiently for comparisons and gotchas. Every token earns its place. | 3 / 3 |
Actionability | Provides fully executable Python code for connections, transactions, and WAL mode. CLI commands are copy-paste ready. The gotchas table gives specific, actionable solutions rather than vague advice. | 3 / 3 |
Workflow Clarity | The skill presents useful patterns but lacks explicit sequencing for multi-step workflows like setting up a new database or migrating. The transaction context manager is good but there's no validation/verification step shown (e.g., checking WAL mode was actually enabled, or verifying schema after creation). | 2 / 3 |
Progressive Disclosure | Clean overview with concise quick-start content, then clearly signaled one-level-deep references to schema patterns, async patterns, and migration patterns. Navigation is straightforward and well-organized. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
9f4534c
- 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.