bun-sqlite
Use for bun:sqlite, SQLite operations, prepared statements, transactions, and queries.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-sqlite/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 effectively identifies its niche (bun:sqlite) with good trigger terms that developers would naturally use, making it distinctive and unlikely to conflict with other skills. However, it lacks specific concrete actions (what it actually helps you do) and reads more like a topic list than a capability description. Adding explicit actions would strengthen it significantly.
Suggestions
Add specific concrete actions like 'Create and manage SQLite databases using bun:sqlite, write prepared statements, handle transactions, build queries, and manage schemas.'
Expand the 'Use when' clause with scenario-based triggers, e.g., 'Use when the user needs to interact with SQLite databases in Bun, write SQL queries, manage database transactions, or use the bun:sqlite API.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (bun:sqlite, SQLite) and some actions (prepared statements, transactions, queries), but doesn't list specific concrete actions like 'create tables', 'run migrations', 'batch insert rows'. The terms are more category-level than action-level. | 2 / 3 |
Completeness | Has a 'Use for/when' clause which addresses when to use it, but the 'what does this do' part is weak — it lists topics rather than concrete capabilities. The 'when' is present but essentially just restates the topic keywords rather than describing scenarios. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'bun:sqlite', 'SQLite', 'prepared statements', 'transactions', 'queries'. These are terms developers naturally use when working with SQLite in Bun. | 3 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to bun:sqlite specifically, which is a distinct niche. Unlikely to conflict with general database skills, other ORM skills, or non-Bun SQLite tools due to the explicit 'bun:sqlite' mention. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-structured skill file with excellent actionability—nearly every concept is backed by executable TypeScript code. The main weaknesses are moderate verbosity (the Repository Pattern and type mapping sections could be trimmed or moved to reference files) and missing validation/error-recovery steps in batch operation workflows. Overall it serves as an effective reference for bun:sqlite usage.
Suggestions
Add explicit validation/error-recovery steps to the Batch Operations section (e.g., wrap in try/catch with rollback guidance) to improve workflow clarity for destructive operations.
Consider moving the Repository Pattern to a separate reference file and linking to it, as it's a lengthy example that inflates the main skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some sections that could be tightened—e.g., the Column Types section explains basic SQLite-to-JS type mappings Claude already knows, the Repository Pattern is quite lengthy for a skill file, and some code comments are redundant. | 2 / 3 |
Actionability | Excellent actionability throughout—every section provides fully executable TypeScript code with concrete examples covering database creation, queries, transactions, error handling, and common patterns. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear sequential workflow, and transactions are well-demonstrated. However, there are no explicit validation checkpoints or error recovery feedback loops for batch/bulk operations, which involve potential data loss scenarios. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers progressing from Quick Start to advanced patterns. References to external files (pragmas.md, fts.md) are clearly signaled at the end with specific trigger conditions, maintaining one-level-deep navigation. | 3 / 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
- secondsky/claude-skills
- Commit
88da5ff
- 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.