cloudflare-d1
Cloudflare D1 SQLite database with Workers, Drizzle ORM, migrations
40
41%
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 ./skills/cloudflare-d1/SKILL.mdQuality
Discovery
40%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 identifies a clear and distinctive technology niche (Cloudflare D1 with Workers and Drizzle ORM), which helps avoid conflicts with other skills. However, it reads as a comma-separated list of technologies rather than a proper description — it lacks concrete actions explaining what the skill does and provides no explicit trigger guidance for when Claude should select it.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates and manages Cloudflare D1 SQLite databases, defines Drizzle ORM schemas, generates and runs migrations, and configures Worker bindings.'
Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about Cloudflare D1 databases, Drizzle ORM setup, D1 migrations, or edge database configuration with Workers.'
Include additional natural trigger terms users might say, such as 'wrangler', 'edge database', 'database schema', 'SQL queries on D1', or 'serverless database'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cloudflare D1 SQLite database) and some associated technologies (Workers, Drizzle ORM, migrations), but doesn't list concrete actions like 'create schemas', 'run migrations', 'query data', or 'configure bindings'. | 2 / 3 |
Completeness | Only lists technologies with no explicit 'what does this do' actions and no 'when should Claude use it' clause. Both the what and when are very weak — it reads more like a tag list than a description. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Cloudflare D1', 'SQLite', 'Workers', 'Drizzle ORM', and 'migrations' that users might mention, but misses common variations like 'database queries', 'schema', 'wrangler', 'bindings', or 'edge database'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Cloudflare D1, Workers, and Drizzle ORM is highly specific and creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent, executable code examples covering the full D1+Drizzle stack. However, it is far too verbose—most of the content (CRUD routes, query patterns, test boilerplate) is standard code Claude can generate without explicit instruction. The skill would benefit enormously from splitting into a concise overview with references to detailed files, and adding explicit validation/error-recovery steps to the migration and deployment workflows.
Suggestions
Reduce the body to ~100 lines covering D1-specific setup (wrangler.toml config, database creation, migration commands) and Drizzle config, moving query patterns, full worker examples, and testing to separate referenced files.
Remove standard CRUD boilerplate and Drizzle query examples that Claude already knows—focus only on D1-specific patterns like batch transactions, the D1Database binding, and edge-specific considerations.
Add explicit validation checkpoints to the migration workflow: verify migration success with a query, include rollback guidance for failed remote migrations, and add a gate between staging and production deploys.
Split content into referenced files (e.g., QUERIES.md, TESTING.md, CLI_REFERENCE.md) and keep SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~450+ lines. It includes extensive CRUD boilerplate, full API route implementations, complete test files, and exhaustive query pattern catalogs that Claude already knows how to write. The component table, limits table, and anti-patterns list add some value, but the bulk of the content (full Hono app, raw D1 worker, every query variant) is standard code Claude can generate without instruction. | 1 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code with concrete commands. Setup steps include exact CLI commands with expected output, schema definitions are complete with type exports, and the migration workflow has specific commands for each environment. | 3 / 3 |
Workflow Clarity | The migration workflow lists steps (generate → apply locally → apply remotely) and includes a dry-run option, but lacks explicit validation checkpoints or error recovery feedback loops. There's no 'verify migration succeeded' step, no guidance on what to do if a migration fails on remote, and the multi-environment deployment sequence doesn't include validation gates between environments. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of content with no references to supporting files. Query patterns, full worker implementations, testing setup, multi-environment config, and CLI reference could all be split into separate files. With no bundle files provided, everything is crammed into one document, making it overwhelming and poorly organized for progressive consumption. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (661 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
7e5f7a2
- 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.