bun-drizzle-integration
Use when integrating Drizzle ORM with Bun's SQLite driver for type-safe schema definitions and migrations.
60
68%
Does it follow best practices?
Impact
—
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 effectively targets a specific technology niche (Drizzle ORM with Bun SQLite) with good trigger terms, but it lacks concrete action descriptions — it only mentions 'schema definitions and migrations' without detailing specific capabilities like defining tables, running queries, or generating migration files. The 'Use when' clause is present but doubles as the entire description, leaving the 'what does this do' aspect underdeveloped.
Suggestions
Add specific concrete actions before the 'Use when' clause, e.g., 'Defines database schemas, generates and runs migrations, configures Drizzle Kit, and sets up type-safe queries using Drizzle ORM with Bun's SQLite driver.'
Expand the 'what' portion to list 2-4 distinct capabilities such as 'create table schemas, push schema changes, generate SQL migrations, configure drizzle.config.ts'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Drizzle ORM, Bun SQLite) and mentions 'type-safe schema definitions and migrations' as actions, 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' is weak — it says 'integrating' but doesn't clearly describe what concrete actions the skill performs. The 'what' and 'when' are conflated into a single clause rather than being distinctly articulated. | 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 help with this specific stack. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of Drizzle ORM + Bun's SQLite driver is a very specific technology stack, making it highly unlikely to conflict with other skills. The trigger terms are narrow and well-targeted. | 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 is a well-structured, highly actionable reference for Drizzle ORM with Bun SQLite that provides executable code for all major operations. Its main weaknesses are verbosity (too much standard Drizzle ORM content that isn't Bun-specific) and a lack of validation checkpoints in the migration workflow. The referenced bundle files don't exist, undermining the progressive disclosure strategy.
Suggestions
Trim standard Drizzle ORM content (CRUD operations, relations, raw SQL, column types) into separate reference files and keep SKILL.md focused on Bun-specific setup, configuration, and the most common patterns.
Add explicit validation steps to the migration workflow, e.g., verifying migration output, checking for errors, and a rollback strategy if migrations fail.
Create the referenced `references/migrations.md` and `references/performance.md` files, or remove the references if they don't exist.
| 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 every variant, 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 Drizzle docs for standard ORM operations. | 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 with rollback, and prepared statements. | 3 / 3 |
Workflow Clarity | The migration workflow lists commands but lacks validation checkpoints — there's no guidance on verifying migration success, handling migration failures, or checking schema state after push. For a skill involving database schema changes (potentially destructive), the absence of feedback loops caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill references `references/migrations.md` and `references/performance.md` at the bottom, which is good progressive disclosure signaling. However, no bundle files exist to back these references, and the main file itself is monolithic (~250 lines) with extensive inline content (full CRUD, relations, transactions, raw SQL, column types) that would be better split into reference files. | 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
5e92b71
- 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.