cloudflare-workers-dev-experience

Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging. Use for project setup, wrangler.jsonc configuration, or encountering local dev, HMR, binding simulation errors.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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.

Highly actionable body with executable configs and commands covering the common Cloudflare Workers dev cases. Verbosity from inlined full config files and broken template references are the main detractors.

Suggestions

Move the full tsconfig.json, package.json scripts, and .vscode/launch.json into reference files and link to them from the body to reduce token weight and improve conciseness.

Either create the referenced templates/wrangler-config.jsonc and templates/dev-script.ts files or remove the Templates table to avoid broken references.

Add a brief validation step to the project setup flow (e.g., run `wrangler types` then `tsc --noEmit` to confirm the scaffold compiles) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body inlines several full config files (tsconfig.json, package.json scripts, .vscode/launch.json) that are token-heavy and arguably belong in references; it is mostly efficient with no concept over-explanation, but could be tightened, so it sits at the midpoint rather than clearly efficient.	3 / 5
Actionability	Provides copy-paste-ready commands and complete config examples throughout (quick start, wrangler.jsonc, wrangler dev flags, wrangler tail, debugging code) covering the common cases, matching the fully-executable top anchor.	5 / 5
Workflow Clarity	The Quick Start and Local Development Workflow give a clear sequenced path; no destructive or batch operations are present that would require validation checkpoints, so the missing explicit validation is a minor gap rather than a cap.	4 / 5
Progressive Disclosure	Good structure with a dedicated, well-signaled "When to Load References" table whose three referenced files all exist; however the Templates table references templates/wrangler-config.jsonc and templates/dev-script.ts that do not exist, and some bulk config is inlined — minor organization gaps keeping it below the top anchor.	4 / 5
	Total	16 / 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, well-scoped description that explicitly answers both what the skill does and when to use it with concrete trigger phrases. Minor room to convert topical terms into more action-oriented verbs and broaden synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capabilities ("local development with Wrangler, Miniflare, hot reload, debugging", "wrangler.jsonc configuration", "binding simulation errors") — multiple specific actions with minor gaps, slightly topic-oriented rather than action-oriented so not a 5.	4 / 5
Completeness	Clearly states what ("Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging") and an explicit "Use for ..." trigger clause with concrete triggers, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("local development", "hot reload", "HMR", "project setup", "binding simulation errors") with synonym coverage, but a few common variants are missing so it sits above the midpoint rather than at comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Cloudflare Workers local dev) with distinct, specific triggers unlikely to fire for unrelated skills, giving minimal conflict risk.	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: secondsky/claude-skills
Path: plugins/cloudflare-workers/skills/cloudflare-workers-dev-experience/SKILL.md
Commit: 84802a4

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