cloudflare-d1

Cloudflare D1 SQLite database with Workers, Drizzle ORM, migrations

Quality

57%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudflare-d1/SKILL.md

Quality

Content

65%

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

The content is highly actionable, with comprehensive executable code and commands for the full D1/Drizzle/Workers workflow. Its weaknesses are mild conceptual padding, missing validation feedback loops around production migrations and deploys, and a monolithic structure that should progressively disclose reference material into separate files.

Suggestions

Trim definitional padding (the D1 Stack table and the 'serverless/zero cold starts' intro) to assume Claude's existing knowledge of these tools.

Add explicit validation feedback loops for risky operations: after applying production migrations, verify with a read query; after deploy, hit a health endpoint before declaring success.

Split the query-patterns and CLI quick-reference sections into bundled reference files (e.g. references/query-patterns.md, references/cli-reference.md) and link to them one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable code and CLI commands that earn their place, but it includes conceptual padding such as the intro ('serverless...global distribution and zero cold starts') and the D1 Stack table defining Workers/Wrangler/Drizzle that Claude already knows. Mostly efficient but could be tightened, so not a 3; not verbose fluff, so above 1.	2 / 3
Actionability	The skill is packed with fully executable, copy-paste-ready code (schema definitions, drizzle config, Hono worker CRUD, raw D1 API, query patterns, transactions) and concrete wrangler/drizzle-kit commands with real flags and file paths. This matches the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Sections are sequenced (setup -> Drizzle -> migrations -> worker) and a --dry-run checkpoint is mentioned for production migrations, but there are no explicit validate->fix->retry feedback loops and deploys lack a verification step. Per the rubric, missing validation for database operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is a single ~650-line monolithic SKILL.md with no bundled reference files (references/scripts/assets absent) and only external doc links; reference material such as the query-patterns and CLI quick-reference sections is inline and could be split out. Well-organized sections keep it above 1, but it is not a simple <50-line skill with one-level-deep references, so not a 3.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 clearly identifies a specific technical niche (Cloudflare D1 with Workers and Drizzle) but reads as a stack label rather than an action-oriented, trigger-rich statement. Adding concrete actions and an explicit 'Use when...' clause would lift it across all dimensions.

Suggestions

Lead with concrete actions, e.g. 'Create and query Cloudflare D1 databases, run Drizzle ORM migrations, and build Workers that read/write D1.'

Append an explicit trigger clause: 'Use when working with Cloudflare D1, D1 databases, Wrangler d1 commands, or Drizzle ORM on Workers.'

Add natural variations users say ('Wrangler d1', 'serverless SQLite', 'edge database') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the concrete domain and stack ('Cloudflare D1 SQLite database', 'Workers', 'Drizzle ORM', 'migrations') but describes a technology list rather than explicit actions (no verbs like create/query/migrate). It is not vague fluff (score 1) yet does not list multiple specific actions (score 3).	2 / 3
Completeness	The description states what the skill covers (the D1 stack) but contains no 'Use when...' trigger clause; that guidance lives in a separate when-to-use frontmatter field. Per the rubric, a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	'Cloudflare D1', 'SQLite', 'Workers', and 'Drizzle ORM' are natural terms a user would say, but common variations like 'Wrangler', 'serverless database', or 'edge database' are missing. Some relevant keywords present, but coverage is not comprehensive enough for a 3.	2 / 3
Distinctiveness Conflict Risk	'Cloudflare D1' is a distinct niche, but the generic 'SQLite database', 'Workers', and 'Drizzle ORM' terms could overlap with sibling skills for those technologies, and the absence of a trigger clause weakens distinctiveness. Somewhat specific but could still overlap, so not a 3.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: fb7c556

Reviewed: 3 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.