cloudflare
Guide for building applications on Cloudflare's edge platform. Use when implementing serverless functions (Workers), edge databases (D1), storage (R2, KV), real-time apps (Durable Objects), AI features (Workers AI, AI Gateway), static sites (Pages), or any edge computing solutions.
78
Quality
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./claude/skills/cloudflare/SKILL.mdQuality
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 clearly identifies the Cloudflare platform focus, lists specific products and capabilities, and provides explicit trigger conditions. The description uses proper third-person voice and includes both common terms (serverless, edge computing) and Cloudflare-specific product names for comprehensive trigger coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'serverless functions (Workers)', 'edge databases (D1)', 'storage (R2, KV)', 'real-time apps (Durable Objects)', 'AI features (Workers AI, AI Gateway)', 'static sites (Pages)', and 'edge computing solutions'. | 3 / 3 |
Completeness | Clearly answers both what ('Guide for building applications on Cloudflare's edge platform') and when ('Use when implementing serverless functions...') with explicit trigger scenarios covering multiple use cases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Cloudflare', 'Workers', 'D1', 'R2', 'KV', 'Durable Objects', 'Workers AI', 'AI Gateway', 'Pages', 'serverless', 'edge computing', 'edge platform'. These are the exact product names and concepts users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Cloudflare-specific product names (Workers, D1, R2, KV, Durable Objects, Pages) that are unique identifiers. Unlikely to conflict with generic cloud or serverless skills due to the specific platform focus. | 3 / 3 |
Total | 12 / 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.
This skill provides highly actionable, executable guidance for Cloudflare development with excellent code examples covering all major products. However, it suffers from being a monolithic document that could benefit significantly from splitting into focused sub-files, and it lacks explicit validation checkpoints in multi-step workflows like deployments and database operations.
Suggestions
Split content into separate files (e.g., STORAGE.md, AI.md, FRAMEWORKS.md, TROUBLESHOOTING.md) and reference them from a concise overview in SKILL.md
Add explicit validation steps to workflows - e.g., after 'wrangler deploy', add 'Verify: wrangler tail to confirm no errors' or 'Test endpoint: curl https://your-worker.workers.dev'
Remove introductory explanations Claude already knows (what edge computing is, what V8 isolates are) and trim the 'When to Use This Skill' section which largely duplicates the description
Add a feedback loop for D1 migrations: 'After schema changes, verify with: wrangler d1 execute my-db --command=".schema"'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude already knows (e.g., 'Cloudflare Developer Platform is a comprehensive edge computing ecosystem...', explaining what V8 isolates are). Many sections could be tightened while preserving utility. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all TypeScript/bash snippets are copy-paste ready with proper imports, bindings, and complete implementations. CLI commands are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Setup workflows are clear with sequential steps, but validation checkpoints are largely missing. For example, database migrations and deployments lack explicit verification steps. The troubleshooting section helps but doesn't integrate validation into the main workflows. | 2 / 3 |
Progressive Disclosure | This is a monolithic 700+ line document with no references to external files. Content that could be split (AI products, framework guides, troubleshooting) is all inline. The Resources section links to external docs but the skill itself lacks internal progressive disclosure. | 1 / 3 |
Total | 8 / 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 (1105 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
- einverne/dotfiles
- Commit
b1b2fe0
- 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.