email-best-practices

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

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/FujishigeTemma/listen --skill email-best-practices-fujishigetemma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/FujishigeTemma/listen/tree/main/.claude/skills/email-best-practices
Command: npx skills add https://github.com/FujishigeTemma/listen --skill email-best-practices-fujishigetemma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you build robust, deliverable, and compliant email systems, preventing emails from going to spam and ensuring legal adherence.

Core Features & Use Cases

  • Deliverability: Set up SPF, DKIM, DMARC to ensure emails reach inboxes.
  • Compliance: Meet CAN-SPAM, GDPR, CASL requirements.
  • Reliability: Implement idempotency and retry logic for sending.
  • Use Case: You're launching a new SaaS product and need to send transactional emails like password resets and order confirmations. This Skill guides you through setting up authentication, handling compliance, and ensuring reliable delivery.

Quick Start

Use the email best practices skill to set up SPF, DKIM, and DMARC for your sending domain.

Frequently Asked Questions about email-best-practices

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

FAQPage Schema
Why do my transactional emails go to spam and how do I fix it?

Transactional emails go to spam due to missing DNS authentication. Set up SPF, DKIM, and DMARC records for your sending domain to verify identity and ensure reliable inbox delivery.

How do I set up SPF, DKIM, and DMARC for email deliverability?

Set up SPF, DKIM, and DMARC by adding specific DNS records to your sending domain. This authentication framework prevents spoofing and proves to providers that your emails are legitimate.

What is the difference between transactional and marketing emails for compliance?

Transactional emails facilitate agreed-upon interactions like password resets, while marketing emails promote content. Differentiating them dictates specific compliance requirements under CAN-SPAM, GDPR, and CASL.

How do I implement retry logic and idempotency for sending emails?

Implement retry logic and idempotency for sending emails to handle transient failures and prevent duplicate delivery. This ensures reliability in production-ready email systems without repeated messages.

Do I need CAN-SPAM, GDPR, and CASL compliance for a new SaaS product?

Yes, SaaS products sending emails must meet CAN-SPAM, GDPR, and CASL compliance. Adhering to these regulations ensures legal email capture, processing, and unsubscribe mechanisms are implemented correctly.

How do I handle email webhooks for sending reliability?

Handle email webhooks to track delivery statuses, bounces, and spam reports in real-time. Processing these events is crucial for maintaining sending reliability and cleaning recipient lists.