bun-sqlite

Use for bun:sqlite, SQLite operations, prepared statements, transactions, and queries.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/bun/skills/bun-sqlite/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The skill is highly actionable with executable examples, but it over-inlines reference material and points to non-existent bundle files, hurting progressive disclosure. Its database/batch workflows also lack validation checkpoints, capping workflow clarity.

Suggestions

Create the referenced bundle files references/pragmas.md and references/fts.md (or remove the references) so the signaled navigation resolves to real content.

Move the Column Types, Column Definitions, and Performance Tips sections into separate reference files and keep SKILL.md as a concise overview pointing to them.

Add explicit validation/verification checkpoints to the transaction and bulk-insert workflows (e.g. verify row counts, check db.inTransaction, re-query to confirm) so destructive/batch operations have feedback loops.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste-ready code, but it re-explains things Claude already knows (the SQLite-to-JS type mapping and inline comments restating obvious behavior), so it could be tightened.	3 / 5
Actionability	Fully executable TypeScript examples cover the common cases (CRUD, prepared statements, named/positional params, transactions, error handling) and are copy-paste ready.	5 / 5
Workflow Clarity	Content is organized by topic rather than as a sequenced workflow, and the database/batch operations (transactions, bulk inserts, deletes) lack validation or verification checkpoints, capping workflow clarity at 3 per the feedback-loop rule.	3 / 5
Progressive Disclosure	A ~345-line body inlines reference material (Column Types, Column Definitions, Performance Tips) that belongs in separate files, and the only two signaled references (references/pragmas.md, references/fts.md) do not actually exist on disk.	2 / 5
	Total	13 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is specific and well-scoped to bun:sqlite, but it lacks an explicit 'Use when...' trigger clause with concrete scenarios, which caps its completeness. It is otherwise strong on distinctiveness and concrete action naming.

Suggestions

Add an explicit 'Use when...' clause naming concrete user scenarios, e.g. 'Use when working with SQLite in Bun, building a database layer, or handling prepared statements and transactions.'

Include natural synonyms and file extensions users might say (e.g. 'database', 'db', '.sqlite', 'SQL') to broaden trigger term coverage.

Tighten the generic 'SQLite operations' into a couple of specific actions to lift specificity toward a comprehensive list.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities (prepared statements, transactions, queries) rather than vague language, though 'SQLite operations' is somewhat generic, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear from the listed capabilities, but there is only a weak 'Use for' cue and no explicit 'Use when...' clause with concrete trigger phrases, so completeness caps at 3 per the judging guideline.	3 / 5
Trigger Term Quality	Natural terms like 'bun:sqlite', 'SQLite', 'prepared statements', 'transactions', and 'queries' are present, but common synonyms/extensions such as 'database', 'db', or '.sqlite' are missing.	4 / 5
Distinctiveness Conflict Risk	Scoping to 'bun:sqlite' carves out a clear, distinct niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/bun/skills/bun-sqlite/SKILL.md
Commit: ad16332

Reviewed: 12 days 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.