Habilidades cloudflare-email-service

📦

cloudflare-email-service

Name: cloudflare-email-service
Author: cloudflare

Revisão do conteúdo r1 Risco Médio ⚙️ Comandos externos🌐 Acesso à rede⚡ Contém scripts

Build Cloudflare Email Workflows

Transactional email setup is easy to misconfigure across Workers, REST APIs, and routing. This skill provides current patterns for sending, receiving, authentication, and deliverability.

Suporta: Claude Codex Code(CC)

⚠️ 50 Ruim

Instalar com meu Agente

Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.

Solicitação do agente

Review the Skillstore skill "cloudflare-email-service" from https://skillstore.io/skills/cloudflare-cloudflare-email-service.md and its manifest at https://skillstore.io/api/skills/cloudflare-cloudflare-email-service/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.

Recursos legíveis por agentes

Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.

Detalhe em Markdown GET /skills/cloudflare-cloudflare-email-service.md manifest assinado GET /api/skills/cloudflare-cloudflare-email-service/manifest lockfile assinado GET /api/skills/cloudflare-cloudflare-email-service/lockfile

Testar

Usando "cloudflare-email-service". Add transactional welcome emails to my Cloudflare Worker.

Resultado esperado:

Add an EMAIL sending binding to the Worker configuration.
Verify the sending domain before deployment.
Send both plain-text and HTML content through the binding.
Handle delivery errors without exposing recipient data.

Usando "cloudflare-email-service". Help me receive support emails and reply after review.

Resultado esperado:

Route the support address to an email handler.
Read and parse the raw stream once.
Store structured message fields in a Durable Object.
Require user approval before sending a threaded reply.

Usando "cloudflare-email-service". Why are messages reaching spam folders?

Resultado esperado:

Verify SPF, DKIM, and DMARC alignment.
Review bounces, suppressions, and delivery analytics.
Use accurate subjects, complete text content, and valid unsubscribe handling where required.

Auditoria de segurança

Risco Médio

v1 • 09/08/2026 Abrir o relatório versionado

All 74 static alerts are false positives caused by Markdown formatting, documented official API calls, Worker handler syntax, or Durable Object SQL APIs. Semantic review found three medium concerns involving untrusted email content, unescaped HTML replies, and sensitive message logging. No malicious prompt injection, credential exfiltration, or arbitrary process execution was found.

Arquivos analisados

1,154

Linhas analisadas

Itens de revisão

Falsos positivos ignorados

Preocupações de segurança confirmadas (3)

Médio

references/routing.md:111 references/routing.md:145-155

Untrusted Email Content Can Reach an AI Workflow

The guide stores inbound email text and suggests notifying an AI agent to draft replies without defining an untrusted-content boundary. Crafted email text could attempt indirect prompt injection before the agent uses reply capabilities.

The guide explicitly combines stored inbound content with optional AI drafting. The agent call is illustrative and commented, so exploitability depends on the implementation.

Médio

references/routing.md:166-179

Reply Content Is Inserted Into HTML Without Escaping

The reply example inserts replyBody directly into an HTML template. Untrusted or AI-generated markup could alter outgoing email content or add tracking and phishing elements.

The direct interpolation into the HTML field is visible in the example, and no escaping or sanitization step is shown.

Médio

references/routing.md:100-105

Inbound Email Contents Are Written to Logs

The parsing example logs the full subject and text of incoming messages. Email bodies can contain personal data, reset links, or secrets that should not enter routine logs.

The example directly passes parsed subject and body text to console.log. The exposure is clear, although retention and access depend on deployment settings.

Fatores de risco

⚙️ Comandos externos (39)

🌐 Acesso à rede (26)

⚡ Contém scripts (1)

references/routing.md:129

Auditado por: codex

Compartilhar e citar este relatório

Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.

Abrir o relatório versionado

Copiar link do relatório

https://skillstore.io/skills/cloudflare-cloudflare-email-service/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/cloudflare-cloudflare-email-service/security.svg)](https://skillstore.io/skills/cloudflare-cloudflare-email-service?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/cloudflare-cloudflare-email-service?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloudflare-cloudflare-email-service/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Cartão incorporável

<iframe src="https://skillstore.io/embed/skills/cloudflare-cloudflare-email-service.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citações acadêmicas (APA · BibTeX · CFF)

Citação APA

cloudflare. (2026). cloudflare-email-service security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudflare-cloudflare-email-service/audits/1

Citação BibTeX

@techreport{cloudflare-cloudflare-cloudflare-email-service-2026,
  author = {cloudflare},
  title = {cloudflare-email-service security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/cloudflare-cloudflare-email-service/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: "cloudflare-email-service security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "cloudflare"
date-released: "2026-08-09"
url: "https://skillstore.io/skills/cloudflare-cloudflare-email-service/audits/1"
identifiers:
  - type: other
    value: "skillstore:cloudflare-cloudflare-email-service:audit:1"
    description: "Skillstore immutable audit report identifier"

Pontuação do Skillstore

Por que esta pontuação Confiança das evidências: Médio

Arquitetura

Manutenibilidade

Conteúdo

Comunidade

Conformidade com a especificação

O que você pode criar

Add Transactional Email

Configure a Worker binding and send account notifications with plain-text and HTML content.

Build an Inbound Support Mailbox

Route incoming messages to a Worker, parse them, store them, and prepare reviewed replies.

Improve Delivery Health

Check authentication records, suppression handling, sending limits, and analytics for a production email domain.

Teste estes prompts

Configure a Worker Binding

Add Cloudflare Email Sending to my Worker. Show the Wrangler configuration and a basic transactional welcome email with text and HTML.

Send Through the REST API

Create a Cloudflare Email Service REST request for my external application. Use environment-based credentials and explain the response states.

Process Incoming Email

Design an Email Routing handler that parses one raw message, validates the sender, stores metadata, and forwards only to verified destinations.

Design a Reviewed AI Mailbox

Design a secure support mailbox using Email Routing, Durable Objects, and an AI drafting agent. Include prompt-injection controls, approval, sanitization, and observability.

Boas práticas

Use Workers bindings when possible and keep REST API tokens in managed secrets.
Verify sending domains and include both plain-text and HTML message bodies.
Treat inbound messages as untrusted and review agent-generated replies before sending.

Evitar

Do not hardcode API tokens or expose them in logs and examples.
Do not use transactional email infrastructure for newsletters or unsolicited bulk messages.
Do not insert untrusted text into outgoing HTML without escaping or sanitization.