What problem does it solve? Cloudflare Email Service launched in 2025 and evolves rapidly, so pre-trained knowledge of its APIs, bindings, and configuration is often outdated or wrong. This Skill guides implementation and troubleshooting of transactional email sending and inbound email routing on Cloudflare by pointing to current documentation and flagging common mistakes. ## Core Features & Use Cases - Sending Emails: Configure the send_email Workers binding, use the REST API with Bearer tokens for external apps, or send via wrangler CLI and MCP tools from coding agents. - Receiving Emails: Build Workers email() handlers for Email Routing with forwarding, replying, rejecting, and MIME parsing via postal-mime, including store-and-reply-later patterns with Durable Objects. - Deliverability & Operations: Manage SPF/DKIM/DMARC, bounce handling, suppression lists, sending limits, and GraphQL analytics for delivery monitoring. - Use Case: A developer needs their Cloudflare Worker to send order confirmation emails and process inbound support replies. The Skill walks them through domain onboarding, binding configuration, handler code, and deliverability checks while avoiding pitfalls like reading message.raw twice. ## Quick Start Ask the agent to set up Cloudflare Email Sending for your domain and write a Worker that sends a transactional email using the send_email binding.