Index of every page on this site: llms.txt
All skills
cloudflare avatar

/cloudflare-email-service

@5108325 official
by cloudflarecloudflare/skills3.4k stars
357
Run it yourself

Implement or troubleshoot Cloudflare Email Sending and Email Routing integrations and their delivery configuration.

Use this Skill: https://skilld.dev/gh/cloudflare/skills/cloudflare-email-service

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesskill-feedback.md

≈708 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Skill feedback

GitHub issues are public: anyone can read an issue once it is posted. Never include sensitive information, and never post an issue until the user has seen the exact title and body and approved it.

Use this when the user reports that the cloudflare-email-service skill gave incorrect or outdated guidance, is missing information, or could be improved. This is about the skill (agent instructions), not about Cloudflare products.

What not to include

The issue is drafted from the conversation, so remove the following before drafting and describe the problem in general terms instead:

  • Credentials, API tokens, secrets, and passwords
  • Account IDs, zone IDs, and other resource identifiers
  • Customer or personal data, such as names, email addresses, and IP addresses
  • Internal hostnames and URLs
  • Private code, configuration, and logs

Steps

  1. Ask permission – Ask the user if they would like to submit feedback to the skill maintainers. If they decline, move on.

  2. Draft the issue – Fill in the table below from the conversation and use it as the issue body. Always identify which specific file and section caused the problem. Leave out everything listed in What not to include.

  3. Review with the user – Show the user the exact title and body, then ask a yes/no question, such as "Post this as a public issue on cloudflare/skills?" Submit only after the user answers yes. If they ask for changes, apply them and ask again. If they answer no, do not post. Agreeing to send feedback in step 1 is not approval of the text.

  4. Submit – Create a GitHub issue on the cloudflare/skills repository with the approved draft as the body, for example with gh issue create --repo cloudflare/skills. The title must follow this format: skill-feedback: cloudflare-email-service: <summary of the problem>.

  5. Share the result – Share the issue URL with the user after submission. If submission fails, give the user the approved title and body, and this link to create the issue manually: https://github.com/cloudflare/skills/issues/new

Issue body

Field Value
Type bug (incorrect guidance), outdated, missing, or improvement
Skill cloudflare-email-service
Source File and section, e.g. SKILL.md > "Section name" or references/<file>.md > "Section name"
Agent The agent and model in use, if known
Task What the user was trying to do, e.g. "deploy a preview"
Expected What should have happened, e.g. "Create a Preview deployment"
Actual What the skill said or what happened, e.g. "Unknown option: --preview"
Impact The effect on the user, e.g. "Time spent finding the correct syntax"
Suggested fix How the skill should change; leave blank if unsure

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning23d4 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    This skill provides guidance for integrating Cloudflare's Email Service, including sending and routing emails. It includes security considerations related to processing untrusted data from incoming emails, a common aspect of email-related tools. The documentation mitigates these risks by recommending human-in-the-loop workflows.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: MEDIUM · 1 issue

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 5108325. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 4 weeks ago
  • Python
  • cloudflare
  • email-sending
  • email-routing
  • workers
  • transactional-email
  • rest-api
  • nodejs
  • golang

README badge

README badge for cloudflare/skills/cloudflare-email-service

Send transactional emails and route incoming messages using Cloudflare Email Service, with Workers bindings, REST API, or the Agents SDK. Use this skill for email setup, authentication (SPF/DKIM/DMARC), deliverability tuning, and integrating email into Workers, Node.js, Python, Go, or any AI coding agent.

Generated from the current SKILL.md.

Does this skill cover both sending and receiving emails?
Yes. It covers Email Sending (transactional emails via Workers binding or REST API) and Email Routing (inbound email handling with the `email()` handler). The references are split by use case.
Can I use this skill outside of Cloudflare Workers?
Yes. The REST API works from Node.js, Python, Go, or any external app. You'll need a Cloudflare API token and account ID instead of a binding.
Do I need to set up my domain before sending?
Yes. The domain must be onboarded to Email Sending first via `wrangler email sending enable yourdomain.com` or the Cloudflare Dashboard. The `from` address must use an onboarded domain.
What's the difference between the Workers binding and the REST API?
The Workers binding requires no API keys and uses camelCase field names (`email`, `replyTo`). The REST API uses snake_case (`address`, `reply_to`) and requires a Bearer token, but works outside Workers.
Can I use this for marketing emails or newsletters?
No. Email Service is for transactional emails only. Use a dedicated marketing platform for bulk sends and campaigns.

Generated from the current SKILL.md. These answers refresh after source changes.