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.

1.13x

Quality

76%

Does it follow best practices?

Impact

100%

1.13x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/sqlite-ops/SKILL.md

Quality

Content

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 skill that provides immediately actionable SQLite patterns for Python. Its strengths are token efficiency and concrete, executable code examples. The main weaknesses are the lack of explicit workflow sequencing for multi-step database operations and the absence of the referenced bundle files that would complete the progressive disclosure structure.

Suggestions

Add the referenced bundle files (schema-patterns.md, async-patterns.md, migration-patterns.md) to complete the progressive disclosure structure.

Consider adding a brief workflow for common multi-step operations like 'new database setup' with validation checkpoints (e.g., verify schema after creation).

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, copy-paste ready Python code for connections, transactions, and WAL mode. CLI commands are concrete and specific. The gotchas table maps problems directly to solutions.	3 / 3
Workflow Clarity	Individual patterns are clear, but there's no explicit workflow sequencing for common multi-step operations like setting up a new database (create connection → set pragmas → create schema → validate). The context manager pattern is good but lacks guidance on when validation/verification should occur, particularly for migration or schema changes.	2 / 3
Progressive Disclosure	References to three detailed pattern files are well-signaled and one-level deep, which is good structure. However, no bundle files were provided, meaning the referenced files (schema-patterns.md, async-patterns.md, migration-patterns.md) don't actually exist, undermining the progressive disclosure. The main content itself is well-organized with clear sections.	2 / 3
	Total	10 / 12 Passed

Description

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, it lacks an 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, 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

Validation

100%

Warnings & errors only

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: c7b7905

Reviewed: about 4 hours ago

Table of Contents

Discovery Implementation Validation

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.