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.
84
76%
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, but falls short on specificity of concrete actions and completeness of when-to-use guidance. The 'Triggers on:' format partially compensates for a missing 'Use when...' clause but doesn't describe user scenarios or tasks explicitly.
Suggestions
Replace the category-level terms ('state management, caching, async operations') with concrete actions like 'Create and manage SQLite schemas, implement caching layers, handle async database operations with aiosqlite, configure WAL mode'.
Add an explicit 'Use when...' clause describing user scenarios, e.g., 'Use when the user needs to set up a local SQLite database in Python, write schema migrations, or configure database connection settings.'
| 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
79%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, concise reference skill that provides immediately actionable SQLite patterns for Python. Its main strengths are token efficiency and executable code examples. Weaknesses include the lack of bundle files to back up the referenced resources and the absence of explicit workflow sequences with validation steps for operations like migrations or schema changes.
Suggestions
Provide the referenced bundle files (schema-patterns.md, async-patterns.md, migration-patterns.md) so the progressive disclosure actually works.
Add a brief sequenced workflow for a common multi-step operation like database setup or migration, including a validation checkpoint (e.g., verify schema after migration with a query).
| 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 gotchas and WAL mode comparison. Every token earns its place. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code for connections, transactions, and CLI usage. The context manager pattern and connection function are complete and immediately usable. | 3 / 3 |
Workflow Clarity | Individual patterns are clear but there's no sequenced workflow for common multi-step operations like setting up a new database, running migrations, or validating schema changes. The skill is more of a reference card than a guided workflow, which is acceptable for the topic but lacks validation checkpoints. | 2 / 3 |
Progressive Disclosure | References to three detailed pattern files are well-signaled at the bottom, but no bundle files were provided, meaning those references point to non-existent resources. The overview content itself is well-structured with clear sections, but the referenced files cannot be verified. | 2 / 3 |
Total | 10 / 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
3ae408c
- 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.