workers-development — Claude Code skill for Workers debugging
The workers-development Claude Code skill runs and debugs Cloudflare Workers locally, then directs production investigations to observability tools. It activates for requests to run or troubleshoot a Worker.
Apache-2.0 8,200 installs ★ 3,424 updated 2026-10-19
npx skills add cloudflare/skills --skill workers-development -a claude-codeWhat workers-development does
The skill starts Cloudflare Workers with the project's existing command: cf dev, a Wrangler script, or the Cloudflare Vite plugin. Local Explorer can read and seed data for KV, R2, D1, SQLite-backed Durable Objects, and Workflows. It can also trigger Cron handlers.
Local Explorer records traces and logs from local invocations, including binding operations. For a deployed Worker, the skill points to Workers observability for logs, traces, or metrics. If the Cloudflare MCP server is connected, it can search for and call Workers Observability API operations.
A binding marked remote: true reaches the deployed resource while the Worker runs locally. Those calls appear in traces too.
What it helps with
- start a Worker with the project's local development command
- inspect or seed local binding data
- find traces and logs for a local request
- investigate production Worker logs, traces, or metrics
- trigger a Cron handler locally
Example prompts for the agent
- Run my Cloudflare Worker locally and investigate the request that fails.
- Inspect local Worker traces and find the binding operations.
- Review production logs and metrics for the deployed Worker.
How to install workers-development
1Skills CLI (Vercel)
npx skills add cloudflare/skills --skill workers-development -a claude-code2Manually: put the files in place
~/.claude/skills/workers-development/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/workers-development/
1Skills CLI (Vercel)
npx skills add cloudflare/skills --skill workers-development -a codex2Manually: put the files in place
.agents/skills/workers-development/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cloudflare/skills --skill workers-development -a cursor2Manually: put the files in place
.cursor/skills/workers-development/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cloudflare/skills skills/workers-development2Manually: put the files in place
.github/skills/workers-development/SKILL.md1Skills CLI (Vercel)
npx skills add cloudflare/skills --skill workers-development -a gemini-cli2Platform CLI
gemini skills install https://github.com/cloudflare/skills --path skills/workers-developmentManually: put the files in place
.devin/skills/workers-development/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cloudflare/skills --skill workers-development -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about workers-development
How do I install workers-development in Claude Code?
Run npx skills add cloudflare/skills --skill workers-development -a claude-code. The skill file is at ~/.claude/skills/workers-development/SKILL.md.
What does workers-development do?
It helps run and troubleshoot Cloudflare Workers locally with the project's tools, and points production investigations to Workers observability. Local Explorer provides access to binding data, traces, and logs.
What happens when a local binding uses remote mode?
A binding set to remote: true accesses the deployed resource even during local execution. Its calls are included in traces.
Source text
SKILL.md · Apache-2.0
--- name: workers-development description: Run, inspect, and debug Cloudflare Workers during local development with cf dev, wrangler dev, or the Cloudflare Vite plugin, using Local Explorer to read and seed binding data and query local traces and logs. Also routes production debugging to Workers observability. Use for debugging requests whether or not the project uses Wrangler. --- # Workers development and debugging Use the project's existing tooling, scripts, and configuration. Installed help, the Local Explorer API schema, and current docs describe the supported operations; read them rather than guessing endpoints or flags. | Need | Tools and discovery | | --- | --- | | Run locally | Use the project's existing dev command: `cf dev` in a `cf` project, otherwise the Wrangler or Cloudflare Vite dev script. See [local development](https://developers.cloudflare.com/workers/local-development/index.md). | | Inspect or seed local binding data | [Local Explorer](https://developers.cloudflare.com/workers/local-development/local-explorer/index.md) is a UI and API for local KV, R2, D1, SQLite-backed Durable Objects, and Workflows, and can trigger Cron handlers. Open `/cdn-cgi/local/explorer` on the dev server's origin. | | Debug local requests | Local Explorer captures traces and logs from every local invocation, including binding operations, without code changes. Check traces before adding logging. | | Debug a deployed Worker | Choose logs, traces, or metrics with [Workers observability](https://developers.cloudflare.com/workers/observability/index.md), or the `cloudflare` skill's observability reference when installed. If the Cloudflare MCP server is connected (bundled with this plugin), use `search` to find the [Workers Observability API](https://developers.cloudflare.com/api/resources/workers/subresources/observability/index.md) operations, then `execute` to call them, scoped to the target account, Worker, and time window. | ## Use the Local Explorer API When the dev server detects an AI agent, including under `cf dev`, it prints a hint with the API URL and relevant endpoints. Fetch the OpenAPI specification from `/cdn-cgi/local/explorer/api` on the dev server's origin, then extract only the operations the task needs. If no hint appears, request that URL directly. If the API or an operation is missing, compare the installed Wrangler or Vite plugin version against the requirements in the Local Explorer docs. Bindings are simulated locally by default, but a binding set to `remote: true` reaches the real deployed resource while the Worker runs locally. Traces also capture those remote calls. Identify which bindings are remote before seeding or writing data. ## Skill feedback If the user reports that this skill gave incorrect or outdated guidance, or is missing information, read [references/skill-feedback.md](references/skill-feedback.md).
© cloudflare · Apache-2.0 · cloudflare/skills