email-best-practices

Configure SPF, DKIM, and DMARC for email deliverability and compliance.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/devkit-stack/Claude --skill email-best-practices-devkit-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/devkit-stack/Claude/tree/main/.claude/skills/email-best-practices
Command: npx skills add https://github.com/devkit-stack/Claude --skill email-best-practices-devkit-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Email sending across apps often suffers from deliverability issues, compliance gaps, and unreliable delivery workflows that waste time and erode trust.

Core Features & Use Cases

  • Deliverability guidance (SPF/DKIM/DMARC setup) to improve inbox placement and reduce spam.
  • Compliance framework covering CAN-SPAM, GDPR, and CASL, including unsubscribe, consent, and data retention.
  • Reliability practices for sending (idempotency, exponential backoff retries) and suppression list management.
  • Observability and automation through webhooks for delivery events, bounces, and complaints.
  • Start-to-finish playbooks for consent capture, lifecycle management, and lifecycle hygiene.

Quick Start

Start by auditing your DNS authentication (SPF, DKIM, DMARC) and drafting a basic compliance and unsubscribe policy, then implement a minimal sending workflow with suppression checks and a webhook listener for delivery events.

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 records to improve email deliverability?

To improve email deliverability, you must configure DNS authentication by adding SPF, DKIM, and DMARC records to your domain. This validates sending servers, prevents spoofing, and directly increases inbox placement rates for transactional and marketing emails.

What is the best way to handle email compliance for CAN-SPAM, GDPR, and CASL?

Email compliance for CAN-SPAM, GDPR, and CASL requires implementing explicit opt-in consent capture, automated unsubscribe mechanisms, and strict data retention policies. This ensures legal adherence when sending marketing emails across different global regions.

How do I stop duplicate emails when retrying failed transactional sends?

To stop duplicate emails during failed transactional retries, implement idempotent sending techniques alongside exponential backoff retry patterns. This guarantees each message is delivered only once, even if the sending workflow triggers multiple attempts.

Why do I need webhook listeners for email bounces and complaints?

You need webhook listeners for email bounces and complaints to automate suppression list hygiene. Processing these delivery events in real-time prevents sending to invalid addresses, protects your sender reputation, and maintains reliable delivery workflows.

Does this email deliverability guidance apply to both marketing and transactional emails?

Yes, this guidance applies to both marketing and transactional emails. It provides start-to-finish playbooks covering DNS authentication, consent lifecycle management, and suppression logic to ensure reliable inbox placement across all sending types.