cloudflare-d1
Build with D1 serverless SQLite database on Cloudflare's edge. Use when: creating databases, writing SQL migrations, querying D1 from Workers, handling relational data, or troubleshooting D1_ERROR, statement too long, migration failures, or query performance issues. Prevents 14 documented errors.
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 follows best practices. It uses third person voice, provides specific concrete actions, includes an explicit 'Use when:' clause with comprehensive triggers, and has highly distinctive terminology that clearly differentiates it from generic database skills. The inclusion of specific error codes and troubleshooting scenarios adds practical value for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating databases, writing SQL migrations, querying D1 from Workers, handling relational data, troubleshooting D1_ERROR, statement too long, migration failures, query performance issues.' These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Build with D1 serverless SQLite database on Cloudflare's edge') and when (explicit 'Use when:' clause with comprehensive trigger scenarios including both creation tasks and troubleshooting scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'D1', 'SQLite', 'Cloudflare', 'SQL migrations', 'Workers', 'relational data', plus specific error terms like 'D1_ERROR', 'statement too long', 'migration failures', 'query performance'. These match what developers would naturally search for. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Cloudflare D1, not generic database skills. The combination of 'D1', 'Cloudflare', 'Workers', and D1-specific error codes makes it unlikely to conflict with other database or SQL 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 D1 skill with excellent executable code examples and clear workflows. The main weakness is its length - at 500+ lines it could benefit from splitting advanced topics into separate files. The content is thorough but occasionally redundant, with the best practices summary largely repeating earlier guidance.
Suggestions
Split advanced topics (Scaling & Limitations, Known Issues table, Wrangler Commands Reference) into separate reference files to reduce main skill length
Remove or consolidate the 'Best Practices Summary' section since these points are already covered inline throughout the document
Move the 'Recent Updates' section to a separate CHANGELOG.md to prevent the main skill from becoming stale
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., best practices summary repeats earlier content) and could be tightened. The 'Recent Updates' section with specific dates adds bulk that may become stale, though it's useful context. | 2 / 3 |
Actionability | Excellent executable code examples throughout - from Quick Start to CRUD operations, pagination, batch patterns, and retry logic. All code is copy-paste ready with proper TypeScript types and real-world patterns. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit validation steps: migrations show local-first testing before production, error handling includes retry patterns with exponential backoff, and the migration workflow has numbered steps with validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a logical flow from Quick Start to advanced topics. However, this is a monolithic 500+ line document that could benefit from splitting advanced topics (sharding, FTS5, error patterns) into separate reference files. | 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 (734 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 | |
- 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.