gateway-workers
Build and Review Cloudflare Gateway Workers
Gateway Forward integrations require entrypoints, context handling, and continuation rules that differ from ordinary Workers. This skill guides implementation and validation using current Cloudflare references.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "gateway-workers" from https://skillstore.io/skills/cloudflare-gateway-workers.md and its manifest at https://skillstore.io/api/skills/cloudflare-gateway-workers/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "gateway-workers". Review a Worker that only implements a default fetch handler.
Resultado esperado:
- The default handler does not implement the Gateway Forward contract.
- Export GatewayMiddleware extending WorkerEntrypoint and implement its handle method.
- Validate the named RPC entrypoint and a permitted request through a scoped Forward policy.
Usando "gateway-workers". Review a Worker that changes the destination and calls next() twice.
Resultado esperado:
- Call next() at most once; it always targets the original destination.
- Destination URL and host changes do not redirect continuation.
- A separate fetch() subrequest does not inherit the user Gateway policies or egress configuration.
Usando "gateway-workers". Review a Worker that trusts identity headers and buffers all response bodies.
Resultado esperado:
- Use Gateway-provided identity instead of client-supplied identity headers.
- Handle rejected identity lookups separately from anonymous identity values.
- Stream response bodies and omit bodies for HEAD requests and statuses 204, 205, and 304.
Auditoría de seguridad
SeguroAll 20 static findings are false positives involving Markdown formatting, documentation links, API terminology, or related-skill references. The skill explains independent subrequest risks and recommends trusted identity, scoped validation, and streaming. No evidence found of prompt injection, credential extraction, malicious execution, or unauthorized data transfer.
Factores de riesgo
⚙️ Comandos externos (7)
🌐 Acceso a red (9)
📁 Acceso al sistema de archivos (3)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/cloudflare-gateway-workers/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/cloudflare-gateway-workers?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/cloudflare-gateway-workers?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloudflare-gateway-workers/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/cloudflare-gateway-workers.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
cloudflare. (2026). gateway-workers security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudflare-gateway-workers/audits/1Cita BibTeX
@techreport{cloudflare-cloudflare-gateway-workers-2026,
author = {cloudflare},
title = {gateway-workers security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cloudflare-gateway-workers/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gateway-workers security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cloudflare"
date-released: "2026-10-25"
url: "https://skillstore.io/skills/cloudflare-gateway-workers/audits/1"
identifiers:
- type: other
value: "skillstore:cloudflare-gateway-workers:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Implement Gateway middleware
Adapt an existing Worker to the named RPC entrypoint and correct continuation contract.
Review identity-dependent behavior
Check identity trust, posture lookups, missing values, and lookup failures before introducing identity-dependent decisions.
Validate a scoped rollout
Plan Gateway integration checks covering policy matching, supported traffic, response handling, and streaming.
Prueba estos prompts
Explain how GatewayMiddleware differs from a default fetch handler, using the current Forward guide.
Review my Worker for zero-or-one next() calls, synthetic responses, and independent fetch() subrequests. Explain any policy inheritance implications.
Review my Gateway identity and posture handling. Distinguish anonymous users, absent posture values, and rejected lookups. Recommend explicit failure behavior.
Create a scoped Gateway test plan for this Worker. Cover RPC entrypoints, continuation, inspection order, streaming, response restrictions, and traffic limitations.
Mejores prácticas
- Consult current Forward documentation and type-check against installed Gateway types before implementation.
- Use Gateway identity and explicitly handle missing context values and rejected lookups.
- Test the named RPC entrypoint and a scoped Gateway path, including continuation and streaming behavior.
Evitar
- Treating a successful direct fetch-handler request as proof that Gateway integration works.
- Using next() to redirect, retry, fan out, or continue more than once.
- Assuming independent fetch() subrequests inherit Gateway policies or egress configuration.
Preguntas frecuentes
Does a default fetch handler implement Gateway Forward?
Can next() redirect a request to another destination?
Do independent fetch() subrequests inherit Gateway policies?
How should identity lookup failures be handled?
Which traffic limitations should I check?
Does this skill deploy or test a Worker automatically?
Detalles del desarrollador
Autor
cloudflareLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Repositorio
https://github.com/cloudflare/skills/tree/86505e44f87d801aa1864a3c4109e9a8ae5c409f/skills/gateway-workersRef.
0596e7dcb24514e7373fb1c8c2a058e2990a6e83
Actualidad del mantenimiento
25/10/2026
Uso
0 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md