agentleFS
salmandevsalmandev/everything-gemini/skills/cloudflare-workers/SKILL.md

cloudflare-workers

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Use this skill when developing Cloudflare Workers, configuring Wrangler v3, integrating Cloudflare D1 SQL or KV storage, or deploying global edge APIs.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use typed Env interfaces and native fetch handlers:

    line 40

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloudflare Workers & Edge Infrastructure

Overview

Cloudflare Workers execute on V8 isolates across 300+ edge locations worldwide. This skill provides architectural patterns for ultra-low latency serverless APIs, D1 relational databases, KV storage, and Wrangler configuration.

Procedural Workflow

1. Project Scaffolding & Wrangler Config

Structure wrangler.jsonc or wrangler.toml with strict environment bindings:

{
  "$schema": "node_modules/wrangler/config-schema.json",
  "name": "edge-api",
  "main": "src/index.ts",
  "compatibility_date": "2024-09-23",
  "compatibility_flags": ["nodejs_compat"],
  "d1_databases": [
    {
      "binding": "DB",
      "database_name": "prod-db",
      "database_id": "xxxx-xxxx"
    }
  ],
  "kv_namespaces": [
    {
      "binding": "CACHE",
      "id": "yyyy-yyyy"
    }
  ]
}

2. Edge Request Handling

Use typed Env interfaces and native fetch handlers:

export interface Env {
  DB: D1Database;
  CACHE: KVNamespace;
  API_SECRET: string;
}

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const url = new URL(request.url);
    if (request.method === "OPTIONS") {
      return handleCors(request);
    }
    // Execution context for background tasks that shouldn't block response
    ctx.waitUntil(logAnalytics(request, env));
    return new Response(JSON.stringify({ status: "ok" }), {
      headers: { "Content-Type": "application/json" }
    });
  }
};

3. Edge Storage Patterns

  • Cloudflare KV: High-read, low-write caching (eventually consistent). Ideal for session tokens, feature flags, and redirect maps.
  • Cloudflare D1: Serverless SQLite at the edge. Always use parameterized queries (env.DB.prepare("SELECT * FROM users WHERE id = ?").bind(id).first()).
  • Cloudflare R2: Zero-egress S3-compatible object storage.

Verification Checklist

  • compatibility_date pinned to a modern version
  • Secrets managed via wrangler secret put, never hardcoded
  • Background telemetry wrapped in ctx.waitUntil
  • D1 queries use parameterized bindings to prevent SQL injection

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.