email-best-practices

Guides implementation of deliverable, compliant transactional and marketing email systems.

5|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/sergiodxa/monorepo --skill email-best-practices-sergiodxa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/sergiodxa/monorepo/tree/main/.agents/skills/email-best-practices
Command: npx skills add https://github.com/sergiodxa/monorepo --skill email-best-practices-sergiodxa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building email features involves navigating deliverability rules, spam filtering, legal compliance (CAN-SPAM, GDPR, CASL), and reliability concerns that are easy to get wrong, leading to emails landing in spam or legal exposure. ## Core Features & Use Cases - Deliverability Setup: Configure SPF, DKIM, and DMARC authentication, warm up sender IPs, and troubleshoot spam placement. - Compliance & Consent: Implement double opt-in, consent records, unsubscribe flows, and retention policies meeting CAN-SPAM, GDPR, and CASL requirements. - Reliable Sending Infrastructure: Apply idempotency keys, exponential backoff retries, webhook signature verification, and suppression list management for bounces and complaints. - Use Case: When adding a password reset flow to a SaaS app, use the transactional email catalog to plan required emails, set up DNS authentication, and implement idempotent sending with webhook-based bounce handling. ## Quick Start Use the email-best-practices skill to plan and implement the transactional emails for my new SaaS app, including authentication setup and bounce handling.

Frequently Asked Questions about email-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up SPF, DKIM, and DMARC for my domain?▼

Add an SPF TXT record listing your sending servers (e.g., v=spf1 include:amazonses.com ~all), publish the DKIM TXT record provided by your email service, and create a DMARC record starting with p=none for monitoring. Verify each with dig TXT commands before sending.

What is the difference between transactional and marketing emails?▼

Transactional emails facilitate a user-initiated action like password resets or order confirmations and can be sent without opt-in. Marketing emails are promotional, require explicit consent, and must include unsubscribe mechanisms under GDPR and CASL.

Why are my emails going to spam?▼

Check authentication first, since Gmail and Yahoo reject unauthenticated email. Then review sender reputation, bounce rates above 4%, complaint rates above 0.05%, and sudden volume spikes using tools like Google Postmaster Tools.

How do I prevent duplicate emails when retrying failed sends?▼

Send a deterministic idempotency key based on the business event, such as password-reset-{userId}-{requestId}, with each request. The email API returns the original response for repeated keys within the cache window instead of sending again.

How should I handle email bounces and complaints?▼

Suppress hard bounces and spam complaints immediately and permanently via webhook events. Retry soft bounces on a 1h, 4h, 24h schedule and suppress after three to five failures. Always check the suppression list before every send.

Do I need double opt-in for my newsletter?▼

Double opt-in is recommended for all marketing lists because it verifies deliverability, confirms intent, and satisfies GDPR and CASL consent requirements. Single opt-in is acceptable for account creation and transactional flows.