cloudflare-worker-builder

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

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

Well-structured, executable guidance that appropriately splits detail into verified reference files and keeps critical gotchas inline. It lands just below top marks on conciseness, actionability, and workflow clarity due to a redundant intro, omitted Queues/auth config examples, and absent explicit verification steps.

Suggestions

Add concrete configuration snippets for Queues bindings and for at least one auth option (Clerk or better-auth) so every binding type asked about in Step 1 has a matching example.

Insert an explicit verification checkpoint after deploy (e.g. 'wrangler deploy' then curl the /api route or check the dashboard) and after 'npm run dev' to confirm the server is live.

Trim the redundant opening paragraph that re-states the frontmatter description, letting the body start directly at the Workflow.

Dimension	Reasoning	Score
Conciseness	Lean and competence-assuming with no padding about what Workers/Hono are, but the opening line ('Scaffold a working Cloudflare Worker project... Produces a deployable project with...') restates the frontmatter description, a minor instance of over-explanation short of the every-token-earns-its-place anchor 5.	4 / 5
Actionability	Provides copy-paste-ready scaffold commands, wrangler/vite configs, and CORRECT/WRONG export patterns, but Step 1 asks about auth (Clerk/better-auth) and the description mentions Queues bindings while neither's concrete configuration appears in the examples — minor gaps short of the fully-covered anchor 5.	4 / 5
Workflow Clarity	A clearly sequenced 4-step workflow (Understand → Scaffold → Configure Bindings → Deploy) reinforced by the Critical Patterns guardrails, but it lacks explicit verification checkpoints (e.g. confirm dev server runs, validate deploy output); not capped at 3 because scaffolding/deploying is not a destructive or batch operation.	4 / 5
Progressive Disclosure	A concise overview with well-signaled, one-level-deep references — 'references/common-issues.md', 'references/architecture.md', 'references/deployment.md' each with a one-line description — and an assets/ bundle whose files (wrangler.jsonc, vite.config.ts, src/index.ts, etc.) all exist and are listed, matching the clear-overview anchor 5.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capability and trigger conditions with concrete, naturally-occurring phrases. It narrowly misses top marks on specificity and trigger-term quality only for minor omissions (testing coverage, synonyms/file extensions).

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Scaffold and deploy', 'scaffold structure, configure bindings, deploy', 'configure D1 / R2 / KV / Queues bindings') with good domain coverage, but 'Describe project' is vague and testing/local-dev are absent — a minor gap short of the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets') and 'when' via a concrete 'Use whenever the user wants to...' clause enumerating multiple triggers, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Strong natural phrases users would say ('create a Worker project', 'set up Hono on Cloudflare', 'configure D1 / R2 / KV / Queues bindings', 'troubleshoot... deployment failures'), but lacks synonyms and file extensions (e.g. .toml/.jsonc) that the anchor 5 example requires.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrowly scoped niche (Cloudflare Workers + Hono + Vite + Static Assets) with triggers unlikely to fire for unrelated skills, giving minimal conflict risk per the anchor 5.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: jezweb/claude-skills
Path: plugins/cloudflare/skills/cloudflare-worker-builder/SKILL.md
Commit: 176df0f

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