cloudflare-d1

Cloudflare D1 SQLite database with Workers, Drizzle ORM, migrations

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/cloudflare-d1/SKILL.md

Quality

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 specific technology stack (Cloudflare D1 + Workers + Drizzle ORM) which gives it good distinctiveness, but it reads more like a tag list than a proper skill description. It lacks concrete actions the skill performs and has no 'Use when...' clause to guide skill selection.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Creates and manages Cloudflare D1 SQLite databases, writes Drizzle ORM schemas, generates and runs migrations, configures Worker bindings.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to set up or query a D1 database, write Drizzle schemas, run database migrations, or configure Cloudflare Workers with database bindings.'

Include additional natural trigger terms users might say, such as 'edge database', 'SQL queries', 'wrangler.toml', 'database schema', 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 tables', 'write queries', 'run migrations', or 'configure bindings'.	2 / 3
Completeness	Lists technologies (the 'what' is only partially addressed as a keyword list rather than capabilities), and completely lacks any 'when to use' guidance. Per rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores 1.	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 schema', 'SQL queries', 'wrangler', 'bindings', or 'edge database'.	2 / 3
Distinctiveness Conflict Risk	The combination of Cloudflare D1, Workers, and Drizzle ORM is a very specific technology stack that is unlikely to conflict with other skills. This creates a clear niche.	3 / 3
	Total	8 / 12 Passed

Implementation

57%

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

The skill is highly actionable with excellent, executable code examples covering the full D1 + Drizzle stack. However, it's a monolithic document that would benefit significantly from progressive disclosure — splitting query patterns, testing, and CLI reference into separate files. The migration workflow lacks explicit validation/error recovery steps, and some introductory content is unnecessary for Claude.

Suggestions

Split content into separate reference files (e.g., QUERIES.md for query patterns, TESTING.md for test setup, CLI.md for command reference) and link from the main skill with clear navigation.

Add explicit validation checkpoints to the migration workflow — e.g., verify migration success before deploying, and include error recovery guidance if remote migration fails.

Remove the introductory paragraph explaining what D1 is and the component table — Claude can infer these from context. Start directly with the Core Principle and Project Setup.

Trim the full CRUD Worker implementation to a minimal example (1-2 routes) and move the complete version to a reference file.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~400+ lines) with extensive inline code examples that could be split into reference files. The introductory sentence explaining what D1 is and the component table add some unnecessary context, but most content is practical. The full CRUD Worker implementation and extensive query patterns could be in separate reference files.	2 / 3
Actionability	Excellent actionability throughout — every section provides fully executable code, specific CLI commands with expected outputs, and copy-paste ready examples covering setup, schema, migrations, worker implementation, queries, testing, and deployment.	3 / 3
Workflow Clarity	The migration workflow lists steps (generate → apply local → apply remote) with a dry-run option, which is good. However, there's no explicit validation checkpoint or error recovery loop — e.g., no guidance on what to do if a migration fails on remote, or verification that migrations succeeded before deploying the worker.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with no references to external files. The schema definition, full CRUD worker implementation, extensive query patterns, testing setup, multi-environment config, and CLI reference are all inline. This would benefit enormously from splitting into separate reference files (e.g., QUERIES.md, TESTING.md, CLI-REFERENCE.md).	1 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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
skill_md_line_count	SKILL.md is long (658 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 24cfe58

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.