Build type-safe D1 databases with Drizzle ORM. Includes schema definition, migrations with Drizzle Kit, relations, and D1 batch API patterns. Prevents 18 errors including SQL BEGIN failures, cascade data loss, 100-parameter limits, and foreign key issues. Use when: defining D1 schemas, managing migrations, bulk inserts, or troubleshooting D1_ERROR, BEGIN TRANSACTION, foreign keys, "too many SQL variables".
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill drizzle-orm-d1Overall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 hits all the marks. It provides specific capabilities (schema definition, migrations, relations, batch API patterns), includes natural trigger terms that users would actually search for (including exact error messages), has an explicit 'Use when:' clause, and is highly distinctive to the D1/Drizzle ecosystem. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'schema definition, migrations with Drizzle Kit, relations, and D1 batch API patterns' plus specific error prevention scenarios including 'SQL BEGIN failures, cascade data loss, 100-parameter limits, and foreign key issues'. | 3 / 3 |
Completeness | Clearly answers both what (build type-safe D1 databases with Drizzle ORM, schema definition, migrations, relations, batch API patterns) AND when with explicit 'Use when:' clause listing specific scenarios and error messages. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'D1 schemas', 'migrations', 'bulk inserts', 'D1_ERROR', 'BEGIN TRANSACTION', 'foreign keys', 'too many SQL variables' - these are exact error messages and common task descriptions users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets D1 databases with Drizzle ORM, includes unique error codes (D1_ERROR, BEGIN TRANSACTION) and platform-specific limits (100-parameter). Unlikely to conflict with generic database or ORM skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent executable code examples and clear validation workflows. The comprehensive issue prevention section (18 documented issues) is valuable but contributes to length that could be better managed through progressive disclosure. The skill excels at preventing real-world errors with concrete solutions.
Suggestions
Move detailed issue descriptions (Issues #1-18) to references/common-errors.md, keeping only a summary table with issue names, error messages, and one-line prevention tips in the main SKILL.md
Remove redundant version information - consolidate to a single 'Package Versions' section rather than repeating in frontmatter, Quick Start comments, and footer
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., version numbers repeated multiple times, verbose issue descriptions that could be condensed). The 18 issues section is valuable but could be more concise with a summary table linking to details. | 2 / 3 |
Actionability | Excellent executable code throughout - Quick Start is copy-paste ready, all issue solutions include working code examples, batch API patterns are concrete, and migration commands are specific. The autochunk function and patch instructions are particularly actionable. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints: Quick Start has numbered steps, migration workflow emphasizes '--local before --remote', Issue #16 provides safe migration pattern with backup/restore sequence, and the flatten-migrations script includes package.json integration. | 3 / 3 |
Progressive Disclosure | References section mentions external files (wrangler-setup.md, schema-patterns.md, etc.) with clear 'when to load' guidance, but the main document is quite long (~500 lines). The 18 issues could be moved to common-errors.md with summaries inline, improving the overview nature of SKILL.md. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (756 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
Table of Contents
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.