wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
84
78%
Does it follow best practices?
Impact
93%
1.34xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/wrangler/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 a strong skill description that clearly identifies its domain (Cloudflare Workers CLI / wrangler), lists comprehensive specific services it covers, and provides explicit trigger guidance for when to load it. The description is concise yet thorough, and the mention of biasing towards Cloudflare docs adds useful behavioral context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete services and actions: 'deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store.' This is highly specific about what the skill covers. | 3 / 3 |
Completeness | Clearly answers 'what' (CLI for deploying, developing, and managing various Cloudflare services) and 'when' ('Load before running wrangler commands to ensure correct syntax and best practices'). The trigger guidance is explicit about when to use it. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Cloudflare Workers', 'wrangler', 'KV', 'R2', 'D1', 'Vectorize', 'Hyperdrive', 'Workers AI', 'Containers', 'Queues', 'Workflows', 'Pipelines', 'Secrets Store'. These are all terms a developer would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Cloudflare Workers and the wrangler CLI. The enumeration of specific Cloudflare services (KV, R2, D1, Vectorize, etc.) makes it very unlikely to conflict with other skills. | 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 excels at actionability with comprehensive, copy-paste ready commands and config examples covering the full Wrangler ecosystem. However, it suffers from being a monolithic reference document (~500+ lines) that should leverage progressive disclosure by splitting per-service details into separate files. Multi-step workflows like deployment, migration, and project setup lack explicit validation checkpoints and sequencing.
Suggestions
Split per-service sections (KV, R2, D1, Vectorize, Hyperdrive, Containers, Workflows, Pipelines, Secrets Store, Pages) into separate reference files and link to them from a concise overview in SKILL.md
Add explicit multi-step workflow sequences with validation checkpoints, e.g., a deployment workflow: 'wrangler types → wrangler types --check → wrangler deploy --dry-run → wrangler deploy → wrangler tail --status error' with error recovery guidance
Add a clear 'New Project Setup' workflow with numbered steps and verification at each stage (init → configure → types → dev → test → deploy)
Trim the full config example to show only 2-3 bindings with a note like 'See [CONFIG_REFERENCE.md] for all binding types' to reduce token usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is largely efficient and avoids explaining basic concepts, but it's quite long (~500+ lines) with extensive command listings for every service (Containers, Pipelines, Secrets Store, etc.) that could be split into separate reference files. Some sections like the full config example with every binding type are verbose when a minimal example plus a reference link would suffice. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides copy-paste ready commands and complete JSONC config snippets. Commands include specific flags, concrete examples, and real patterns (e.g., migration workflows, secret management with security notes, vitest config). | 3 / 3 |
Workflow Clarity | While individual commands are clear, multi-step workflows lack explicit validation checkpoints and feedback loops. For example, the deployment workflow doesn't sequence 'types → dry-run → deploy → verify', and the D1 migration workflow doesn't include validation between local and remote apply steps. The Quick Start section is just two commands with no follow-up verification. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no bundle files to offload detailed reference material. The per-service command references (KV, R2, D1, Vectorize, Hyperdrive, Containers, Workflows, Pipelines, Secrets Store, Pages) would be much better as separate files linked from a concise overview. This is a wall of text that consumes significant context window. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (923 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- cloudflare/skills
- Commit
60147cb
- 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.