Cloudflare Workers
SkillCloud & infraThis skill gives your AI the correct patterns for writing and debugging Cloudflare Workers code. Once added, your AI can build Workers that use KV, Durable Objects, R2, D1, and Queues the right way, and set up and deploy them with wrangler. It also covers WebSockets, streaming responses, and the limits that apply at deploy time.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then ask your AI to write or fix a Cloudflare Worker, mentioning the parts you use such as KV, Durable Objects, or wrangler.
Then ask your AI: use the Cloudflare Workers skill
What your AI can do with it
- Write Workers code using correct runtime patterns
- Store and read data with KV, R2, and D1
- Build stateful features with Durable Objects and message handling with Queues
- Set up WebSockets and streaming responses
- Configure and deploy with wrangler while staying within deployment limits
What this skill tells your AI
The instructions your AI receives, as published by epicenterhq/epicenter in .agents/skills/cloudflare-workers/SKILL.md and read by ahel’s review.
Reference Repositories
- Cloudflare Docs - Workers, Durable Objects, KV, R2, D1, Queues, WebSockets, bindings, and deployment docs
- Hono - TypeScript web framework commonly used on Workers
Upstream Grounding
When Worker runtime behavior, bindings, Durable Objects, WebSockets, streaming, cache APIs, service bindings, compatibility dates, limits, or wrangler configuration affect correctness, ask DeepWiki a narrow question against cloudflare/cloudflare-docs before relying on memory. Use honojs/hono as the grounding repo when the question is about Hono on Workers.
Verify decisive details against local generated Worker types, source, or official Cloudflare docs before changing code. Skip DeepWiki for stable Web API basics and repo-local deployment patterns already visible in the code.
Request Lifecycle Rules
- Every async side effect must be awaited, returned, or passed to
c.executionCtx.waitUntil(...). Floating promises are unsafe because the isolate can stop after the response. - Call
waitUntilas a method onc.executionCtx. Do not destructure it. - Keep
waitUntilwork bounded and best-effort. Use Queues for guaranteed or long-running work. - For Hyperdrive plus
pg, create a freshpg.Clientper request and close it after all queued work that uses the client settles. Hyperdrive is the pool. - Node-style database drivers require
nodejs_compatin Worker configuration. - Skip generic response-header middleware, including CORS, for WebSocket upgrade requests. The
101response headers are immutable. - Put stateful or long-lived WebSockets in Durable Objects. Prefer hibernation-aware APIs when the object owns many idle sockets.
- Trust generated Worker binding types such as
Cloudflare.Env; regenerate them when bindings orwranglerconfig change.
Signals
- GitHub stars
- 5k
- Forks
- 379
- Last commit
- Sep 2026
ahel review
S4info
community integration — published by epicenterhq, not cloudflare
Automated review, not a security audit. Ruleset v1.
Advanced
- Catalog kind
- skill
- Gateway key
cloudflare-workers-epicenterhq- Source
- github.com/epicenterhq/epicenter