Skip to content
cccskills
FreePublished on GitHub

gateway-workers

Build, debug, or review Cloudflare Workers called by the Forward action in Gateway HTTP policies. The skill guides the `GatewayMiddleware` entry point, Gateway context, request continuation, and response handling within the documented limits.

OriginalShow the original description

Build, debug, or review Cloudflare Workers invoked by the Forward action in Gateway HTTP policies, including the GatewayMiddleware entrypoint, Gateway types, context, and continuation.

fcakyon/claude-codex-settings1,192 stars(GitHub 1,192 + cccskills 0)
Works withCloudflare

Run score Not tested

See how to install

Good for

  • Implementing a Worker for a Gateway Forward policy
  • Reviewing Gateway middleware and context handling
  • Debugging request continuation or synthetic responses
  • Checking a Worker against Gateway traffic limitations

Files included (1)

  • SKILL.md4.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Gateway Workers

Read the current Forward guide before implementing a Worker. It defines how Gateway invokes Workers on permitted HTTP traffic. Retrieve the relevant page below rather than copying setup, API payloads, or limits into the project from memory.

Workflow

  1. Inspect the existing Worker and choose a Worker template for the required transformation, synthetic response, or background task.
  2. Export a named GatewayMiddleware class extending WorkerEntrypoint from cloudflare:workers. Implement handle(request, context, next) and return a Response. Gateway calls this method through RPC. A default fetch() handler alone does not implement the Forward contract.
  3. For TypeScript, follow the chosen template's current package installation and type-import instructions.
  4. Use the second argument for Gateway context. It describes the original request and stays unchanged when the Worker modifies the request. Keep it distinct from this.ctx (Workers execution context) and this.env (bindings).
  5. Continue the user's request with next(request) at most once, or return a synthetic response without calling it. next() always targets the original destination. Changes to the destination URL or host are ignored, and it cannot redirect, retry, or fan out. Use fetch() to send a request to a different destination. It creates an independent subrequest that does not inherit the user's Gateway policies or egress configuration.

Context

Use the published types and context reference for field names and availability. Treat a falsy identity (!identity) as anonymous and guard optional posture values. Call await context.identity() or await context.devicePosture() only when needed. Both getters can reject. Catch lookup failures separately from missing values and decide how to handle each when the Worker depends on them. Use Gateway-provided identity rather than client-supplied identity headers.

Gateway behavior

  • Only the first matching Forward policy invokes a Worker. Worker invocation does not confirm successful body inspection. Follow the Forward guide's inspection order.
  • Gateway inspects the final response, including synthetic responses. Modified request bytes are not inspected again before reaching the origin.
  • Review the Forward guide's limitations before choosing traffic: HTTPS requires decryption, WebSockets bypass the Worker, and matching Workers VPC traffic is dropped. Worker invocation failures fail closed.

Validation

Type-check against the installed Gateway types and test the named RPC entrypoint, including zero or one continuation call and the context values the Worker uses. Then test a permitted request through a scoped Gateway Forward policy. A direct request to a default fetch() handler does not validate the Gateway path. Follow the chosen template's test procedure and the Forward guide's troubleshooting steps.

Check the response and streaming rules: return a final status from 200 to 599, return no body for HEAD requests or statuses 204, 205, and 304, and stream bodies rather than buffering them.

Related skills

  • cloudflare-one: Gateway policy design, traffic paths, identity, TLS, and rollout.
  • workers-best-practices: streaming, bindings, generated environment types, background work, observability, and runtime tests.
  • CLI selection: choose the existing cf-cli or wrangler skill for project setup and deployment.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Format responses for readers who benefit from concise, visible steps and low-friction starts. It puts the answer first, breaks work into short numbered actions, tracks progress, and adds brief educational notes around code changes while keeping secondary details separate.

  • Format a reply as short numbered steps
  • Make a long task easier to follow
  • Keep responses concise and show progress
fcakyon/claude-codex-settings1.2KUpdated Oct 27, 2026

agent-browser

FreeSummary

Use this skill to automate browser tasks such as opening websites, reading page content, clicking controls, filling forms, signing in, extracting data, and taking screenshots. It explains a snapshot-based workflow for interacting with pages and handling tabs and waits.

  • Filling out a website form
  • Extracting information from a web page
  • Capturing a page screenshot
fcakyon/claude-codex-settings1.2KUpdated Oct 27, 2026

agents-sdk

FreeSummary

Build, debug, or review applications built with Cloudflare’s Agents SDK and the `agents` package. It covers agent state, routing, chat, scheduled and durable work, and integrations, while consulting current Cloudflare documentation for implementation details.

  • Starting an Agents SDK application
  • Adding agents to an existing Workers project
  • Debugging state or routing behavior
fcakyon/claude-codex-settings1.2KUpdated Oct 27, 2026

Use this skill to plan and build web interfaces with a visual direction tied to the project. It guides choices for color, typography, layout, motion, and interface text, then encourages a review against the brief so the result feels deliberate and specific.

  • Designing a new web interface around a product brief
  • Refreshing an existing page with a distinct visual direction
  • Choosing type, color, and layout for a landing page
fcakyon/claude-codex-settings1.2KUpdated Oct 27, 2026

azure-usage

FreeSummary

Work with Azure resources through Azure MCP: list and inspect storage, Key Vault, Cosmos DB, and AKS resources, manage secrets, upload blobs, and query Log Analytics. It helps choose the operation that fits the task and requires Azure authentication.

  • Listing Azure storage accounts and blobs
  • Managing Key Vault secrets
  • Querying Cosmos DB documents or Log Analytics
fcakyon/claude-codex-settings1.2KUpdated Oct 27, 2026

basin

FreeSummary

Build and troubleshoot Cloudflare Basin data workflows: stream and transform events into Iceberg tables in R2, manage table catalogs, and query the data with SQL. It also helps with resources still referred to by the former Data Platform product names.

  • Stream event data into Iceberg tables stored in R2
  • Manage table metadata and access through Basin Catalog
  • Query R2 Iceberg data with Basin SQL
fcakyon/claude-codex-settings1.2KUpdated Oct 27, 2026

See all skills by fcakyon

Report a problem with this skill