Cloudflare Email Service
Implement or debug Cloudflare Email Service sending, Email Routing, or an Agents SDK email handler. Use for the Workers email binding, Email Service REST API, SMTP, inbound `email()` handlers, domain onboarding, deliverability, or Cloudflare email tooling. Do not trigger for provider-neutral email design or non-Cloudflare mail services.
Install
npx skills add swyxio/skills --skill cloudflare-email-servicegit clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/cloudflare-email-service ~/.claude/skills/cloudflare-email-servicePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cloudflare Email Service Retrieve current Cloudflare documentation and installed Workers types before using API signatures, limits, pricing, or CLI commands. Email Service is evolving and the Workers binding, REST API, SMTP, and Email Routing have distinct contracts. ## Choose the surface | Need | Use | Reference | | --- | --- | --- | | Send from a Worker | Email binding | [sending.md](references/sending.md) | | Send from outside Workers | REST API or SMTP | [rest-api.md](references/rest-api.md) | | Receive, forward, reject, or parse mail | Email Routing `email()` handler | [routing.md](references/routing.md) | | Configure domains or agent tooling | Wrangler/API/MCP setup | [cli-and-mcp.md](references/cli-and-mcp.md) | | Diagnose bounces, authentication, or reputation | Deliverability | [deliverability.md](references/deliverability.md) | Prefer the Worker binding inside Workers unless the existing application already has a reason to use another supported surface. Do not invent one request shape for all surfaces: field names and response envelopes differ. ## Verify prerequisites and boundaries - Resolve the exact account, domain, environment, and sending or routing configuration before changing provider state. - Confirm the sending domain is onboarded and that the target Worker environment has the required binding. - Keep API tokens and message secrets in the platform's secret mechanism, never in source or diagnostic output.
Details
- Skill name
cloudflare-email-service- Repository
- swyxio/skills
- Path
cloudflare-email-service/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Cloudflare Email Service skill do?
Implement or debug Cloudflare Email Service sending, Email Routing, or an Agents SDK email handler. Use for the Workers email binding, Email Service REST API, SMTP, inbound `email()` handlers, domain onboarding, deliverability, or Cloudflare email tooling. Do not trigger for provider-neutral email design or non-Cloudflare mail services.
How do I install the Cloudflare Email Service skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill cloudflare-email-service. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cloudflare Email Service popular?
It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.
Related skills
Accelevents API
201swyxio/skills
Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.
Accelevents Speaker Sync
201swyxio/skills
Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.
Agents SDK
201swyxio/skills
Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.
Cloudflare One
201swyxio/skills
Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs.
Cloudflare Do Turn Based Multiplayer
201swyxio/skills
Design, implement, debug, or verify a remote turn-based multiplayer game whose rooms run on Cloudflare Durable Objects. Use for room and invite identity, reconnectable seats, WebSocket hibernation, concurrent turns, action idempotency, revision conflicts, or cross-browser game-state agreement. Do not trigger for generic Durable Object applications or local-only games.
Cloudflare One Migrations
201swyxio/skills
Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or SASE stacks to Cloudflare One. Use for migration assessments, policy mapping, rollout plans, and parity/gap analysis.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.