tech-drizzle
Drizzle ORM schema design, relational queries, and migration patterns. Use when working with Drizzle ORM, writing database queries, or managing Drizzle migrations.
75
62%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/tech-drizzle/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Drizzle ORM) and includes an explicit 'Use when...' clause with relevant trigger terms. The main weakness is that the capabilities could be more specific with concrete actions rather than general categories. Overall, it should effectively help Claude select this skill when users work with Drizzle ORM.
Suggestions
Expand specificity by listing concrete actions like 'define table schemas', 'set up one-to-many relations', 'generate and run migrations', 'write type-safe queries'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Drizzle ORM) and mentions three areas (schema design, relational queries, migration patterns), but these are somewhat general categories rather than multiple specific concrete actions like 'create tables', 'define relations', 'generate migration files'. | 2 / 3 |
Completeness | Clearly answers both what (schema design, relational queries, migration patterns) AND when (explicit 'Use when...' clause with triggers: working with Drizzle ORM, writing database queries, managing Drizzle migrations). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Drizzle ORM', 'database queries', 'Drizzle migrations', 'schema design'. These cover the main terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Drizzle ORM specifically, which distinguishes it from other database/ORM skills (e.g., Prisma, TypeORM, raw SQL). The repeated 'Drizzle' mentions create a distinct niche unlikely to conflict. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is a meta-template about skill triggering and troubleshooting rather than actual Drizzle ORM guidance. It lacks any concrete code examples, schema patterns, migration commands, or Drizzle-specific instructions. The content would be identical for any skill topic if you replaced 'tech-drizzle' with another name.
Suggestions
Add concrete Drizzle schema examples showing table definitions, relations, and type inference patterns
Include executable migration workflow with specific drizzle-kit commands (e.g., `npx drizzle-kit generate`, `npx drizzle-kit migrate`)
Replace generic troubleshooting with Drizzle-specific issues (e.g., relation type errors, migration conflicts, query builder patterns)
Add a quick-start section with copy-paste ready code for common Drizzle patterns (defining tables, one-to-many relations, queries with joins)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but contains boilerplate troubleshooting sections that don't add Drizzle-specific value. The actual technical guidance is deferred to an external rules file rather than being present. | 2 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The skill describes what to do abstractly ('Use tech-drizzle guidance', 'Apply the skill rules') without showing any actual Drizzle ORM patterns, schema definitions, or migration commands. | 1 / 3 |
Workflow Clarity | A 3-step workflow is provided but it's generic and abstract. Steps like 'Apply the skill rules' and 'Validate output quality' lack specificity for Drizzle ORM tasks. No validation checkpoints specific to database migrations or schema changes. | 2 / 3 |
Progressive Disclosure | References an external rules index file which is appropriate, but the SKILL.md itself contains no substantive overview content. The skill body is mostly meta-instructions about skill triggering rather than Drizzle-specific guidance. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- ravnhq/ai-toolkit
- Commit
7b466be
- 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.