email-best-practices

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

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/kshehadeh/createspot --skill email-best-practices-kshehadeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/kshehadeh/createspot/tree/main/.agents/skills/email-best-practices
Command: npx skills add https://github.com/kshehadeh/createspot --skill email-best-practices-kshehadeh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers build production-ready email systems by addressing deliverability, compliance, and reliability challenges, ensuring emails reach inboxes and meet legal requirements.

Core Features & Use Cases

  • Deliverability: Guides through setting up SPF, DKIM, DMARC to avoid spam filters.
  • Compliance: Details requirements for CAN-SPAM, GDPR, CASL for global reach.
  • Reliability: Implements idempotency and retry logic to prevent duplicate sends and handle failures.
  • Use Case: A developer needs to send password reset emails. This Skill provides the exact steps to configure DNS records, design the email for clarity, and implement retry logic in case of temporary API errors.

Quick Start

Use the email-best-practices skill to set up SPF, DKIM, and DMARC records 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
How do I set up SPF, DKIM, and DMARC records for transactional email deliverability?

To ensure transactional email deliverability, configure SPF, DKIM, and DMARC DNS records for your sending domain. This authenticates outgoing emails, helping them bypass spam filters and reliably reach recipient inboxes.

What is the difference between transactional and marketing email for CAN-SPAM and GDPR compliance?

Transactional emails provide essential account information like password resets, while marketing emails promote services. CAN-SPAM, GDPR, and CASL compliance rules differ significantly between these categories, primarily affecting consent requirements and mandatory unsubscribe mechanisms.

How do I implement retry logic and idempotency to prevent duplicate email sends?

Implement idempotency and retry logic in your email sending architecture to handle temporary API failures safely. This reliability pattern prevents duplicate transactional emails from being dispatched during network timeouts or service disruptions.

Do I need to process email webhooks differently for marketing versus transactional systems?

Processing email webhooks requires handling delivery events and bounces for both transactional and marketing systems. You must parse these payloads to update delivery statuses and maintain reliable, compliant email infrastructure.

What's the best way to ensure global email compliance when sending to international users?

Ensuring global email compliance requires adhering to CAN-SPAM, GDPR, and CASL regulations simultaneously. You must implement proper consent tracking, physical address inclusion, and clear unsubscribe mechanisms across all outbound emails.