mcpbeat

Email Best Practices

resend/email-best-practices-email-best-practices

Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, making emails accessible (alt text, headings, contrast, screen readers), or deciding transactional vs marketing.

19k tokens
context cost
the whole folder, loaded on every use
20
files
instructions only
1
copies elsewhere
how many repositories repackaged it
136
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/resend/email-best-practices --skill email-best-practices

The instruction itself

4 sections, as written by the author

Email Best Practices

Guidance for building deliverable, compliant, user-friendly emails.

Architecture Overview

[User] → [Email Form] → [Validation] → [Double Opt-In]
                                              ↓
                                    [Consent Recorded]
                                              ↓
[Suppression Check] ←──────────────[Ready to Send]
        ↓
[Idempotent Send + Retry] ──────→ [Email API]
                                       ↓
                              [Webhook Events]
                                       ↓
              ┌────────┬────────┬─────────────┐
              ↓        ↓        ↓             ↓
         Delivered  Bounced  Complained  Opened/Clicked
                       ↓        ↓
              [Suppression List Updated]
                       ↓
              [List Hygiene Jobs]

Quick Reference

| Need to... | See |

|------------|-----|

| Set up SPF/DKIM/DMARC, fix spam issues | Deliverability |

| Build password reset, OTP, confirmations | Transactional Emails |

| Plan which emails your app needs | Transactional Email Catalog |

| Build newsletter signup, validate emails | Email Capture |

| Send newsletters, promotions | Marketing Emails |

| Ensure CAN-SPAM/GDPR/CASL compliance | Compliance |

| Decide transactional vs marketing | Email Types |

| Handle retries, idempotency, errors | Sending Reliability |

| Process delivery events, set up webhooks | Webhooks & Events |

| Manage bounces, complaints, suppression | List Management |

| Make emails accessible (screen readers, alt text, contrast) | Accessibility |

Start Here

New app?

Start with the Catalog to plan which emails your app needs (password reset, verification, etc.), then set up Deliverability (DNS authentication) before sending your first email.

Spam issues?

Check Deliverability first—authentication problems are the most common cause. Gmail/Yahoo reject unauthenticated emails.

Marketing emails?

Follow this path: Email Capture (collect consent) → Compliance (legal requirements) → Marketing Emails (best practices).

Production-ready sending?

Add reliability: Sending Reliability (retry + idempotency) → Webhooks & Events (track delivery) → List Management (handle bounces).

Accessibility?

Most emails fail basic accessibility checks. See Accessibility for lang/dir, presentational tables, headings, alt text, <title>, and contrast.

Repackaged in 1 other repositories

same content, different owner
resend/resend-skills open on GitHub →

How to use it

Copy the folder

Take resend/email-best-practices-email-best-practices from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.