CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/drizzle-best-practices

Drizzle ORM patterns -- schema definition, indexes, relations, migrations, transactions, upserts, prepared statements, and connection setup

96

1.60x
Quality

96%

Does it follow best practices?

Impact

98%

1.60x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Discovery

100%

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 an excellent skill description that follows best practices. It uses third person voice, lists specific concrete capabilities, includes natural trigger terms, has an explicit 'Use when...' clause with multiple scenarios, and is clearly distinguishable from other database-related skills by naming Drizzle ORM specifically.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'schema definition, type-safe queries, relations, migrations, transactions, upserts, prepared statements, and connection setup' - these are all distinct, actionable capabilities.

3 / 3

Completeness

Clearly answers both what (Drizzle ORM patterns with specific capabilities listed) AND when (explicit 'Use when...' clause covering building/reviewing apps, new database setup, writing queries/migrations, and production configuration).

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'Drizzle ORM', 'schema', 'queries', 'migrations', 'transactions', 'database', 'production' - covers both the tool name and common database development terms.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive by naming 'Drizzle ORM' specifically - this clearly differentiates it from other database/ORM skills (e.g., Prisma, TypeORM, raw SQL). The specific tool name creates a clear niche.

3 / 3

Total

12

/

12

Passed

Implementation

92%

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

This is an excellent, highly actionable skill document that efficiently teaches Drizzle ORM patterns through concrete WRONG vs RIGHT examples. The content is dense but well-organized, with executable code throughout and a comprehensive checklist for validation. The only weakness is the monolithic structure—for a document this comprehensive, splitting into overview + detailed reference files would improve navigation.

Suggestions

Consider splitting into SKILL.md (overview + quick start) and separate files for detailed topics like RELATIONS.md, MIGRATIONS.md, and QUERIES.md to improve progressive disclosure

Add a brief 'Quick Start' section at the top with the minimal setup (connection + one query) before diving into comprehensive patterns

DimensionReasoningScore

Conciseness

Extremely efficient use of tokens. Every section shows WRONG vs RIGHT patterns without explaining what Drizzle is or how ORMs work. Assumes Claude's competence and focuses only on Drizzle-specific gotchas and patterns.

3 / 3

Actionability

All code examples are fully executable, copy-paste ready TypeScript. Includes complete schema definitions, query patterns, configuration files, and connection setup with real imports and proper syntax.

3 / 3

Workflow Clarity

Clear sequencing for migrations (generate → migrate), explicit validation checkpoints (checklist at end), and warnings about common pitfalls (use tx not db in transactions, destructure returning()). The WRONG vs RIGHT format makes the correct workflow unambiguous.

3 / 3

Progressive Disclosure

Content is well-organized with clear section headers and a comprehensive checklist, but it's a monolithic document. References to verifiers at the end are good, but the 400+ line document could benefit from splitting advanced topics (relations, prepared statements) into separate files.

2 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Reviewed

Table of Contents