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 strong trigger terms covering library names and key concepts. However, it lacks specific concrete actions (listing what patterns it teaches) and would benefit from a more explicit 'Use when...' clause rather than just a trigger word list. The capability description reads more as a topic summary than an actionable skill guide.
Suggestions
Replace the category-level terms ('state management, caching, async operations') with concrete actions like 'Create database schemas, write migrations, configure WAL mode, implement async database access with aiosqlite, set up caching layers'.
Add an explicit 'Use when...' clause describing scenarios, e.g., 'Use when the user needs to set up or work with SQLite databases in Python projects, including schema design, data migrations, or async database operations.'
| 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 this skill should be selected over other database-related skills. | 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 specific concepts (WAL mode, migrations) 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 efficiently covers SQLite fundamentals with executable code, useful reference tables, and clear pointers to detailed resources. Its main weakness is the lack of an integrated workflow showing how the pieces fit together (e.g., initial setup → schema creation → validation), which would help for more complex database operations. Overall it's concise, actionable, and well-organized.
Suggestions
Consider adding a brief integrated workflow showing the typical sequence: create connection → set pragmas → create schema → use transaction context manager → verify with CLI commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what SQLite is or how Python works. The tables efficiently convey comparison information, and code examples are minimal but complete. | 3 / 3 |
Actionability | Provides fully executable Python code for connection setup, transaction management, and WAL mode. CLI commands are copy-paste ready. The gotchas table gives specific, actionable solutions rather than vague advice. | 3 / 3 |
Workflow Clarity | Individual patterns are clear, but there's no sequenced workflow for setting up a new SQLite database from scratch (create → schema → configure pragmas → validate). The context manager pattern is shown but not integrated into a workflow showing when/how to use it with the connection pattern. | 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. Content is appropriately split between the overview and reference files. | 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.
f772de4
Table of Contents
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.