email-best-practices
Skill10 starsChanged 3 months agoMITView on GitHub
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.
12 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- Groundmail/groundmail-skillstheir own version, first seen Oct 17, 2026
- gerald-donkor/poli-intelword for word, first seen Oct 11, 2026
- sirakinb/claude-code-skillsedited, first seen Oct 11, 2026
- usenotra/notraword for word, first seen Oct 9, 2026
- mezotv/notraword for word, first seen Oct 8, 2026
- novuhq/novuedited, first seen Oct 8, 2026
Used with
Projects with it also use ai-sdk, vercel-composition-patterns and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillai-sdk
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Also in 3 projects that use this
SentrySkillvercel-composition-patterns
Also in 3 projects that use this
Microsoft AzureSkillhumanizer
Tone enforcement patterns for external-facing community responses
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 7
- mezotv/notra★ 256100% same
- usenotra/notra★ 256100% same
- resend/resend-skills★ 212100% same
- nezaboravi/orkestar★ 2100% same
- gerald-donkor/poli-intel★ 1100% same
- sprioleau/flock★ 1100% same
- swsounds42/claude-dotfiles★ 0100% same
Edited · 3
- novuhq/novu★ 40k69% same
- utxo-AG/claude-skills★ 269% same
- sirakinb/claude-code-skills★ 169% same
Wrote their own version · 2
- danest/emailbump-skills★ 0same name
- Groundmail/groundmail-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- public/llms.txtllms.txt
- ab-testingSkill
- ad-creativeSkill
- adsSkill
- agent-email-inboxSkill
- ai-seoSkill
- analyticsSkill
- animation-vocabularySkill
- apple-designSkill
- asoSkill
- attributionSkill
- churn-preventionSkill
- cold-emailSkill
- co-marketingSkill
- community-marketingSkill
- competitor-profilingSkill
- competitorsSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- croSkill
- customer-researchSkill
- design-taste-frontendSkill
- directory-submissionsSkill
- emailsSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- free-toolsSkill
- grill-meSkill
- imageSkill
- improve-animationsSkill
- influencer-marketingSkill
- interactivity-best-practicesSkill
- launchSkill
- lead-magnetsSkill
- marketing-councilSkill
- marketing-ideasSkill
- marketing-loopsSkill
- marketing-planSkill
- marketing-psychologySkill
- next-cache-components-optimizerSkill
- offersSkill
- onboardingSkill
- paywallsSkill
- popupsSkill
- pricingSkill
- product-marketingSkill
- programmatic-seoSkill
- prospectingSkill
- public-relationsSkill
- react-emailSkill
- referralsSkill
- remocnSkill
- remotion-best-practicesSkill
- resend-cliSkill
- resendSkill
- review-animationsSkill
- revopsSkill
- sales-enablementSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 4 are common, 0 are distinctive, and 0 are very specific to this project.
4
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 61
Start with the Catalog to plan which emails your app needs (password reset, verification, etc.), then set up Deliverability (DNS …
- Common: line 64
Check Deliverability first—authentication problems are the most common cause.
- Common: line 67
Follow this path: Email Capture (collect consent) → Compliance (legal requirements) → Marketing Emails (best practices).
- Common: line 70
Add reliability: Sending Reliability (retry + idempotency) → Webhooks & Events (track delivery) → List Management (handle bounces).
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

