
Cloudflare Workers
- 53 installs
- 31 repo stars
- Updated April 12, 2026
- itallstartedwithaidea/agent-skills
cloudflare-workers is an agent skill that teaches edge-first Workers patterns with Durable Objects, D1, KV, R2, AI, and Vectorize.
About
cloudflare-workers is an agent skill for solo builders who want APIs, AI agents, and lightweight SaaS on Cloudflare’s edge instead of a traditional always-on server. It encodes how Workers behave in V8 isolates—stateless routing at the edge plus Durable Objects for coordination—and walks through KV, R2, D1, AI bindings, and Vectorize with patterns drawn from real production Workers. Invoke it when you are implementing backends, integrations, or agent tooling during Build, and again when you Operate or Ship performance-sensitive global deploys. The skill emphasizes constraints agents often get wrong: no filesystem, actor-style state, and binding-first configuration. Intermediate familiarity with HTTP and JavaScript/TypeScript helps; the payoff is architecture that matches Cloudflare’s platform rather than lifted Node monoliths.
- Edge V8 isolate model: 300+ locations, sub-ms cold starts, no container/process assumptions
- Durable Objects as single-threaded actors with SQLite, WebSockets, and alarms for stateful coordination
- Production patterns from googleadsagent.ai stacks: AI orchestration, D1/Vectorize knowledge, edge content generation
- Guidance across KV, R2, D1, AI bindings, and Vectorize for correct globally distributed architecture
Cloudflare Workers by the numbers
- 53 all-time installs (skills.sh)
- +3 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #708 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill cloudflare-workersAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 53 |
|---|---|
| repo stars | ★ 31 |
| Security audit | 3 / 3 scanners passed |
| Last updated | April 12, 2026 |
| Repository | itallstartedwithaidea/agent-skills ↗ |
What it does
Design and implement edge-first APIs and agents on Cloudflare Workers with Durable Objects, D1, KV, R2, AI bindings, and Vectorize using production patterns.
Who is it for?
Best when you're shipping AI agents, APIs, or content engines on Cloudflare with D1, Vectorize, or Durable Objects.
Skip if: Pure static frontends on Vercel only, or teams committed to long-lived Kubernetes services with no edge interest.
When should I use this skill?
Building or refactoring Cloudflare Workers that need Durable Objects, distributed storage, or AI bindings instead of traditional server architecture.
What you get
You ship Worker handlers and Durable Object designs with correct bindings, storage choices, and coordination patterns suitable for production edge deploys.
- Worker route handlers with correct bindings
- Durable Object coordination design
- Storage binding choices documented in implementation
By the numbers
- 300+ edge locations
- Sub-millisecond cold starts cited in skill positioning
Files
Cloudflare Workers
Part of Agent Skills™ by googleadsagent.ai™
Description
Cloudflare Workers provides comprehensive guidance for building edge-first applications using Durable Objects, KV, R2, D1, AI bindings, and Vectorize. This skill encodes production patterns from real Workers powering googleadsagent.ai™, including buddy-agent (AI orchestration), buddy-brain (knowledge storage with D1/Vectorize), and blog-engine (static content generation at the edge).
Workers run in V8 isolates at 300+ edge locations with sub-millisecond cold starts and no container overhead. This fundamentally changes application architecture: computation moves to the user, state lives in globally distributed storage, and traditional server concepts (processes, threads, file systems) do not apply. The agent must understand these constraints to produce correct, performant Worker code.
Durable Objects provide the stateful coordination layer that Workers alone lack. Each Durable Object instance is a single-threaded actor with transactional SQLite storage, WebSocket support, and alarm scheduling. The combination of stateless Workers for routing and stateful Durable Objects for coordination is the foundational pattern for all non-trivial edge applications.
Use When
- Building serverless APIs on Cloudflare Workers
- Implementing stateful coordination with Durable Objects
- Storing data in KV, R2, D1, or Vectorize
- Using Workers AI for inference at the edge
- Deploying applications similar to googleadsagent.ai™'s architecture
- Migrating from traditional server architectures to edge-first
How It Works
graph TD
A[Client Request] --> B[Worker: Route + Auth]
B --> C{Request Type}
C -->|API| D[Durable Object: buddy-agent]
C -->|Content| E[KV: Cached Pages]
C -->|Upload| F[R2: Object Storage]
C -->|Query| G[D1: SQLite Database]
D --> H[Workers AI: Inference]
D --> I[Vectorize: Embeddings]
G --> J[buddy-brain: Knowledge Base]
E --> K[blog-engine: Page Serving]
H --> L[Response to Client]
I --> L
J --> L
K --> LThe Worker acts as the stateless router. It authenticates requests, determines the appropriate binding, and delegates to the specialized storage or compute layer. Durable Objects handle coordination that requires strong consistency (sessions, queues, rate limiting).
Implementation
export default {
async fetch(request: Request, env: Env): Promise<Response> {
const url = new URL(request.url);
if (url.pathname.startsWith("/api/chat")) {
const id = env.BUDDY_AGENT.idFromName("default");
const agent = env.BUDDY_AGENT.get(id);
return agent.fetch(request);
}
const cached = await env.PAGE_CACHE.get(url.pathname);
if (cached) return new Response(cached, {
headers: { "Content-Type": "text/html", "Cache-Control": "public, max-age=3600" },
});
return new Response("Not Found", { status: 404 });
},
} satisfies ExportedHandler<Env>;
export class BuddyAgent extends DurableObject {
async fetch(request: Request): Promise<Response> {
const body = await request.json<{ message: string }>();
const embedding = await this.env.AI.run("@cf/baai/bge-base-en-v1.5", {
text: [body.message],
});
const similar = await this.env.VECTORIZE.query(embedding.data[0], {
topK: 5,
returnMetadata: "all",
});
const context = similar.matches.map(m => m.metadata?.text).join("\n");
const response = await this.env.AI.run("@cf/meta/llama-3.1-8b-instruct", {
messages: [
{ role: "system", content: `Context: ${context}` },
{ role: "user", content: body.message },
],
});
return Response.json({ reply: response.response });
}
}// wrangler.jsonc
{
"name": "buddy-agent",
"main": "src/index.ts",
"compatibility_date": "2026-04-01",
"durable_objects": {
"bindings": [{ "name": "BUDDY_AGENT", "class_name": "BuddyAgent" }]
},
"kv_namespaces": [{ "binding": "PAGE_CACHE", "id": "abc123" }],
"vectorize": [{ "binding": "VECTORIZE", "index_name": "buddy-brain" }],
"ai": { "binding": "AI" }
}Best Practices
- Never use global mutable state in Workers—isolates may be recycled between requests
- Stream large responses instead of buffering them in memory (128MB limit)
- Use
waitUntil()for background work that should not block the response - Pin
compatibility_dateand advance it deliberately, not automatically - Place Durable Objects in a
locationHintnear your primary user base - Store secrets in Wrangler secrets (
wrangler secret put), never invars
Platform Compatibility
| Platform | Support | Notes |
|---|---|---|
| Cursor | Full | Wrangler CLI integration |
| VS Code | Full | Cloudflare extension available |
| Windsurf | Full | Workers-aware deployment |
| Claude Code | Full | Shell + wrangler access |
| Cline | Full | Terminal-based development |
| aider | Partial | Config file generation |
Related Skills
- Edge Rendering
- Observability
- Service Discovery
- Sandbox Hardening
Keywords
cloudflare-workers durable-objects kv r2 d1 workers-ai vectorize edge-computing serverless buddy-agent
---
© 2026 googleadsagent.ai™ | Agent Skills™ | MIT License
Related skills
How it compares
Platform architecture skill for Cloudflare Workers—not generic Express-on-a-VM backend tutorials.
FAQ
Who is cloudflare-workers for?
Developers using agent coding tools to deploy on Cloudflare who need Durable Objects, storage bindings, and AI at the edge without reinventing platform rules.
When should I use cloudflare-workers?
While building backend routes and agent orchestration in Build, when hardening global deploy and perf in Ship, and when iterating production Workers bindings in Operate.
Is cloudflare-workers safe to install?
It is documentation and patterns for your own Workers account—check the Security Audits panel on this page and never paste production API tokens into untrusted skill bundles.