cloudflare-hyperdrive
Connect Workers to PostgreSQL/MySQL with Hyperdrive's global pooling and caching. Use when: connecting to existing databases, setting up connection pools, using node-postgres/mysql2, integrating Drizzle/Prisma, or troubleshooting pool acquisition failures, TLS errors, or nodejs_compat missing. Prevents 11 documented errors.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill cloudflare-hyperdrive87
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 uses third person voice, provides specific capabilities, includes an explicit 'Use when:' clause with diverse trigger scenarios, and targets a clear technical niche (Cloudflare Hyperdrive database connections). The mention of '11 documented errors' adds credibility and specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Connect Workers to PostgreSQL/MySQL', 'global pooling and caching', 'setting up connection pools', 'integrating Drizzle/Prisma', and troubleshooting specific errors like 'pool acquisition failures, TLS errors'. | 3 / 3 |
Completeness | Clearly answers both what ('Connect Workers to PostgreSQL/MySQL with Hyperdrive's global pooling and caching') and when (explicit 'Use when:' clause listing five specific scenarios including troubleshooting cases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PostgreSQL', 'MySQL', 'connection pools', 'node-postgres', 'mysql2', 'Drizzle', 'Prisma', 'TLS errors', 'nodejs_compat', 'Hyperdrive'. These are specific technical terms users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting Cloudflare Workers + Hyperdrive + specific databases. The combination of 'Hyperdrive', 'Workers', and specific ORMs/drivers creates a distinct trigger profile unlikely to conflict with generic database 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 workflows. The Known Issues Prevention section is particularly valuable for preventing real-world problems. However, the skill's length could be reduced by moving detailed reference content (Known Issues, Wrangler commands, troubleshooting) to separate files while keeping summaries in the main skill.
Suggestions
Move the detailed Known Issues section to a separate 'known-issues.md' file, keeping only a summary table with links in the main skill
Extract the Wrangler Commands Reference and Unsupported Features sections to 'references/commands.md' and 'references/limitations.md' respectively
Remove duplicate Prisma warning content - it appears fully in both Known Issues #6 and the ORM Integration section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill is comprehensive and well-organized, it includes some redundancy (e.g., the Prisma warning appears in both Known Issues #6 and the ORM Integration section with nearly identical code examples). The Known Issues section, while valuable, adds significant length that could be condensed or moved to a separate reference file. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples throughout, specific bash commands for setup, complete TypeScript examples with proper typing, and copy-paste ready configurations. Every major pattern includes working code with correct imports and error handling. | 3 / 3 |
Workflow Clarity | The Quick Start section provides a clear 5-step numbered workflow with explicit validation (save the ID, deploy). Critical rules are clearly separated into 'Always Do' and 'Never Do' checklists. Connection cleanup patterns include explicit ctx.waitUntil() requirements with reasoning. | 3 / 3 |
Progressive Disclosure | The skill references external files (references/troubleshooting.md) and external documentation links appropriately, but the main file is quite long (~700 lines). The Known Issues section (11 detailed issues) could be moved to a separate reference file with just a summary in the main skill. Some content like the full Wrangler commands reference could also be externalized. | 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 (815 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.