bun-drizzle-integration
Use when integrating Drizzle ORM with Bun's SQLite driver for type-safe schema definitions and migrations.
75
68%
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-drizzle-integration/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 has strong trigger terms and a clear niche but lacks specificity about what concrete actions the skill enables. It reads more as a 'when to use' statement without adequately describing the capabilities (e.g., defining schemas, generating migrations, querying data). The description would benefit from explicitly listing what the skill does before stating when to use it.
Suggestions
Add concrete actions before the 'Use when' clause, e.g., 'Defines database schemas, generates and runs migrations, and configures Drizzle ORM with Bun's SQLite driver.'
Expand the 'what' portion to list specific capabilities like creating tables, writing queries, handling relations, or configuring drizzle-kit.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Drizzle ORM, Bun SQLite) and mentions 'type-safe schema definitions and migrations' but doesn't list multiple concrete actions like creating tables, running queries, generating migration files, etc. | 2 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when', but the 'what does this do' part is weak — it only says 'integrating' without describing concrete capabilities. The what and when are conflated into a single clause rather than clearly answering both. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Drizzle ORM', 'Bun', 'SQLite', 'schema definitions', 'migrations', and 'type-safe'. These are terms developers would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Drizzle ORM + Bun's SQLite driver is a very specific niche that is unlikely to conflict with other skills. The technology stack is clearly identified. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable code examples for Drizzle ORM with Bun's SQLite driver, covering setup through advanced usage. However, it's overly comprehensive for a SKILL.md file—much of the CRUD, raw SQL, and column type content is standard Drizzle documentation that Claude already knows and could be offloaded to reference files. The workflow for setup and migrations lacks explicit sequencing and validation checkpoints.
Suggestions
Trim the CRUD operations, raw SQL, and column types sections significantly—focus the main file on Bun-specific setup (schema, db init, config, migrations) and move standard Drizzle patterns to a reference file like `references/drizzle-patterns.md`.
Add explicit numbered workflow steps for the initial setup and migration process, including a validation checkpoint (e.g., 'Verify migration generated correctly by reviewing the SQL in ./drizzle/ before applying').
Move the Column Types Reference table to a separate reference file and link to it, keeping the main skill lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some sections that are overly exhaustive for a skill file (e.g., full CRUD operations with many variants, column types reference, raw SQL examples). Much of this is standard Drizzle ORM usage that Claude would know; the Bun-specific integration points are relatively small. The content could be significantly tightened by focusing on Bun-specific setup and linking to references for standard Drizzle patterns. | 2 / 3 |
Actionability | All code examples are concrete, executable TypeScript with proper imports and realistic usage patterns. Commands are copy-paste ready, and the examples cover real-world scenarios including upserts, transactions, prepared statements, and relations. | 3 / 3 |
Workflow Clarity | The setup workflow (install → schema → config → migrate) is implicitly sequenced through section ordering but lacks explicit step numbering or validation checkpoints. For migrations specifically—a potentially destructive operation—there's no validation/verification step (e.g., checking migration output, verifying schema state after push). | 2 / 3 |
Progressive Disclosure | The file references `references/migrations.md` and `references/performance.md` at the end, which is good progressive disclosure. However, the main file itself is quite long (~250 lines) with extensive inline content (full CRUD examples, column types reference, raw SQL) that could be split into reference files. The references section at the bottom is well-structured but the body content should be more concise with more offloading. | 2 / 3 |
Total | 9 / 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.