Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Cloudflare Workers Production Pack

    1

    Eight agent skills and two scripts that make your AI agent ship Cloudflare Workers right: wrangler config, D1, R2, KV, Queues, Durable Objects, limits, CI.

    $24

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Cloudflare Workers Production Pack

    Cloudflare Workers Production Pack

    Example session with this skill installed

    We're about to do our first production deploy. Staging returns 500s with env.DB is undefined. Here's wrangler.jsonc. Fix it.

    {
      "name": "orders_api",
      "main": "src/index.ts",
      "compatibility_date": "2025-11-03",
      "routes": [{ "pattern": "api.example.com/*", "custom_domain": true }],
      "vars": { "ENVIRONMENT": "production", "STRIPE_SECRET_KEY": "<redacted>" },
      "d1_databases": [{ "binding": "DB", "database_name": "orders", "database_id": "<D1_ID>" }],
      "durable_objects": { "bindings": [{ "name": "RATE_LIMITER", "class_name": "RateLimiter" }] },
      "migrations": [{ "tag": "v1", "new_classes": ["RateLimiter"] }],
      "env": {
        "staging": {
          "vars": { "ENVIRONMENT": "staging" }
        }
      }
    }
    
    • Read your context and instructions
    • Compiled the cloudflare workers production

    The agent loads cloudflare-workers-production, then workers-wrangler-config, and runs the linter:

    $ node lint-wrangler-config.mjs wrangler.jsonc
    ERROR name-invalid name "orders_api" may contain only letters, digits and dashes (no underscores).
    WARN  compat-date-old compatibility_date 2025-11-03 is 344 days old. Read the compatibility flags changelog, bump it, run tests and `wrangler types`.
    ERROR secret-in-vars top level: var STRIPE_SECRET_KEY has a secret-like name. Move it to a secret (`wrangler secret put STRIPE_SECRET_KEY`) and .dev.vars for local dev.
    ERROR custom-domain-pattern top level: custom domain "api.example.com/*" contains a wildcard. Custom Domains match one exact hostname.
    ERROR custom-domain-pattern top level: custom domain "api.example.com/*" contains a path. Custom Domains take the whole hostname; use a route for path matching.
    WARN  do-legacy-storage migration v1: new_classes creates a key-value backed class (RateLimiter). Use new_sqlite_classes for new classes.
    WARN  env-missing-binding env.staging: vars entry STRIPE_SECRET_KEY exists at the top level but not in this environment.
    WARN  env-missing-binding env.staging: "durable_objects" is set at the top level but not in this environment. Bindings and vars are not inherited; this environment deploys without them.
    WARN  env-missing-binding env.staging: "d1_databases" is set at the top level but not in this environment. Bindings and vars are not inherited; this environment deploys without them.
    WARN  env-inherits-routes env.staging: inherits the top-level routes (api.example.com/*). Deploying it moves those routes and custom domains to the environment's Worker. Give it its own routes or "routes": [].
    INFO  observability-unset observability is not set. New Workers default to logs on, but set "observability": { "enabled": true } so the config stays the source of truth.
    INFO  secrets-undeclared No secrets.required list. Declare secret names so `wrangler deploy` fails when one is missing and `wrangler types` types them without .dev.vars.
    WARN  types-missing No generated types file (worker-configuration.d.ts). Run `wrangler types` and commit the output; run `wrangler types --check` in CI.
    4 error(s), 7 warning(s), 2 note(s)
    

    It explains the 500s: d1_databases and durable_objects are not inherited by env.staging, so the staging Worker has no DB. It flags two problems that would have hit production next: staging inherits routes, so wrangler deploy --env staging would move api.example.com to the staging Worker, and new_classes would create the rate limiter on the key-value backend, which can never be converted to SQLite. Since nothing is deployed yet, it declares the class in exports with SQLite storage, moves the Stripe key to a secret, and gives staging its own bindings and domain:

    {
      "$schema": "./node_modules/wrangler/config-schema.json",
      "name": "orders-api",
      "main": "src/index.ts",
      "compatibility_date": "2026-10-01",
      "workers_dev": false,
      "preview_urls": false,
      "observability": { "enabled": true, "head_sampling_rate": 1 },
      "routes": [{ "pattern": "api.example.com", "custom_domain": true }],
      "exports": {
        "RateLimiter": { "type": "durable-object", "storage": "sqlite" }
      },
      "secrets": { "required": ["STRIPE_SECRET_KEY"] },
      "vars": { "ENVIRONMENT": "production" },
      "d1_databases": [
        { "binding": "DB", "database_name": "orders", "database_id": "<PRODUCTION_D1_ID>" }
      ],
      "durable_objects": {
        "bindings": [{ "name": "RATE_LIMITER", "class_name": "RateLimiter" }]
      },
      "env": {
        "staging": {
          "routes": [{ "pattern": "staging-api.example.com", "custom_domain": true }],
          "secrets": { "required": ["STRIPE_SECRET_KEY"] },
          "vars": { "ENVIRONMENT": "staging" },
          "d1_databases": [
            { "binding": "DB", "database_name": "orders-staging", "database_id": "<STAGING_D1_ID>" }
          ],
          "durable_objects": {
            "bindings": [{ "name": "RATE_LIMITER", "class_name": "RateLimiter" }]
          }
        }
      }
    }
    

    It sets the secret per environment with npx wrangler secret put STRIPE_SECRET_KEY --env staging, puts the local value in .dev.vars, runs npx wrangler types (which now types STRIPE_SECRET_KEY: string and ENVIRONMENT: "staging" | "production"), and reruns the checks:

    $ node lint-wrangler-config.mjs wrangler.jsonc
    0 error(s), 0 warning(s), 0 note(s)
    
    $ npx wrangler deploy --dry-run --env staging
    Total Upload: 0.45 KiB / gzip: 0.29 KiB
    Your Worker has access to the following bindings:
    Binding                                Resource
    env.RATE_LIMITER (RateLimiter)         Durable Object
    env.DB (orders-staging)                D1 Database
    env.ENVIRONMENT ("staging")            Environment Variable
    --dry-run: exiting now.
    

    Both configs, the linter output and the dry-run output above are real runs on wrangler 4.150.0. Finally it adds wrangler types --check, the D1 migrations apply --remote step and the deploy to CI from workers-testing-release.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Agents write a Worker's fetch handler well. They get production wrong: a staging environment that deploys without its D1 binding because bindings are not inherited, a staging deploy that takes the production Custom Domain because routes are, an API key in vars, BEGIN TRANSACTION in D1, wrangler d1 migrations apply without --remote in CI (it succeeds and changes nothing), KV used as a counter, a queue consumer that throws and redelivers the whole batch, Durable Objects on the key-value backend that can never move to SQLite, test setups built on defineWorkersConfig that the current Vitest integration removed, and size limits quoted from three years ago.

    This pack gives the agent current rules, checked against the Cloudflare developer docs, the wrangler 4.150 config schema and CLI help, and the package source:

    • cloudflare-workers-production: routing, pre-flight checklist, current versions, the boundaries that change behaviour.
    • workers-wrangler-config: wrangler.jsonc, compatibility dates and flags, environments, vars vs secrets and secrets.required, wrangler types, Custom Domains vs routes vs workers.dev, Version URLs.
    • workers-d1-hyperdrive: migrations, prepared statements, batch transactions, retryable errors, read replication, Time Travel, the foreign-key cascade trap in table rebuilds; Hyperdrive with node-postgres and Postgres.js.
    • workers-r2-kv: conditional and range reads, multipart uploads, presigned URLs with a signed content type, bucket CORS, KV consistency and when not to use KV.
    • workers-queues-workflows: per-message ack and retry, idempotent consumers, dead letter queues, Workflows steps, retries, waitForEvent, rollback handlers.
    • workers-durable-objects: SQLite storage, the exports field, alarms, WebSocket hibernation, RPC, retry rules, duration billing.
    • workers-limits-caching: CPU, memory, subrequests, size and startup limits with docs page and date, pricing gotchas, Workers Cache, Cache API, Cache Rules precedence.
    • workers-testing-release: @cloudflare/vitest-plugin, D1 migrations in tests, MSW mocking, GitHub Actions deploys, gradual rollouts, rollbacks, logs, tail, traces.

    Two zero-dependency Node scripts: lint-wrangler-config.mjs flags old compatibility dates, secrets in vars, bindings missing from environments, inherited routes, bad Custom Domain patterns, Durable Object storage mistakes and stale generated types; check-worker-limits.mjs reads a dry-run bundle and the config and warns on size, CPU, env var, asset and subrequest limits for your plan.

    Works with Claude Code (skills folder or plugin), Codex, Gemini CLI and Cursor. Plain Agent Skills format.

    Versions: wrangler 4.150, @cloudflare/workers-types 5.x, @cloudflare/vitest-plugin 1.4 with Vitest 4.1 or 5, cloudflare/wrangler-action v4. Reviewed after Wrangler releases that change config or deploys and after limits or pricing changes.

    Scripts need Node.js 22+. Nothing in the pack was deployed to a live Cloudflare account; deploy, rollback, tail and gradual rollout steps follow the docs and wrangler 4.150 CLI help. Where Cloudflare's own docs disagree (Free-plan Durable Object storage, Workflows concurrency), the pack shows both values. Targets TypeScript or JavaScript Workers on wrangler 4.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    wrangler
    Node.js
    vitest
    tsc
    @cloudflare/codemods

    Permissions

    Terminal / Shell
    Network Access
    Read Files

    File Scopes

    wrangler.jsonc
    wrangler.toml
    src/**
    .github/workflows/**

    The two scripts only read the files you pass them (wrangler config and a dry-run bundle folder). They make no network calls and start no processes. The agent runs wrangler commands in your terminal when you ask it to deploy or test.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Agents write a fetch handler fine but carry stale production facts: old size limits, nodejs_compat rules from before 2026-08-04, migrations instead of the exports field, defineWorkersConfig from the old Vitest integration. The pack gives current rules checked against the Cloudflare docs and wrangler 4.150, plus a config linter that catches the deploy traps.

    One entry skill with seven guides (wrangler config, D1 and Hyperdrive, R2 and KV, Queues and Workflows, Durable Objects, limits and caching, testing and release) and two zero-dependency Node scripts: lint-wrangler-config.mjs and check-worker-limits.mjs.

    The guides cover both formats and use wrangler.jsonc in examples, which Cloudflare now recommends. The linter fully checks wrangler.jsonc and wrangler.json; for wrangler.toml it checks only the compatibility date and suggests converting.

    @cloudflare/vitest-plugin 1.4 with Vitest 4.1 or 5, the current package. It also covers moving off the old @cloudflare/vitest-pool-workers setup.

    No. They only read local files. You need your own account to deploy, as usual.

    New in DevOps & Cloud