email-best-practices

Plan and implement production-ready email systems with DNS authentication and webhook processing.

Updated Jan 6, 2026

Search Tags:#compliance #email #webhooks #idempotency #retry #deliverability #list-management

Ready to run

npx skills add https://github.com/marcosmlslira/observadordedominios --skill email-best-practices-marcosmlslira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/marcosmlslira/observadordedominios/tree/main/.agents/skills/email-best-practices
Command: npx skills add https://github.com/marcosmlslira/observadordedominios --skill email-best-practices-marcosmlslira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams in building production-ready email capabilities by addressing deliverability, compliance, and reliability, helping reduce spam placement and improve user trust.

Core Features & Use Cases

DNS authentication setup (SPF, DKIM, DMARC), sender reputation, and domain provisioning.
Transactional vs marketing planning, consent, unsubscribe management, and webhook processing.
Reliability and operational practices including idempotent sending, retry strategies, and robust error handling.
End-to-end workflows for handling bounces, complaints, suppression lists, and list hygiene across regions.

Quick Start

Review the SKILL.md and begin with the Deliverability, Compliance, and Reliability resources to implement a production-ready email system.

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 DNS authentication for transactional email sending?▼

DNS authentication for email sending requires configuring SPF, DKIM, and DMARC records to verify domain ownership. Proper DNS provisioning establishes sender reputation, reduces spam placement, and ensures transactional emails reach user inboxes reliably.

What is the best way to handle email webhook processing and validation?▼

Email webhook processing requires robust validation and idempotent handling to prevent duplicate actions. Implementing strong observability and retry logic ensures webhook events from email providers are processed reliably even during network failures or service disruptions.

How do I manage suppression lists and email bounce handling for compliance?▼

Suppression lists and bounce handling require tracking email addresses that generated hard bounces or spam complaints. Maintaining list hygiene across regions and automatically suppressing failed addresses ensures ongoing email compliance and protects sender reputation.

Why do I need idempotent sending and retry logic in email systems?▼

Idempotent sending and retry logic prevent duplicate email delivery when network timeouts or transient errors occur. Implementing reliable retry strategies with robust error handling ensures production email systems maintain deliverability without sending multiple copies to recipients.

How do I separate transactional vs marketing email flows for compliance?▼

Transactional and marketing email flows require separate infrastructure to manage consent and unsubscribe rules properly. Planning distinct sender identities, domain provisioning, and lifecycle management for each type ensures regulatory compliance and improves overall deliverability rates.