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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design and operate email sending features that avoid spam filtering, reduce bounces and complaints, and meet legal compliance requirements across major regions.

Core Features & Use Cases

  • Deliverability & authentication: Plan and implement SPF, DKIM, and DMARC, plus sender reputation practices like warming and infrastructure separation.
  • Compliance & consent: Apply CAN-SPAM, GDPR, and CASL requirements, including unsubscribe and consent record rules, with non-legal-advice guidance.
  • Email capture & list hygiene: Validate emails, run double opt-in flows, manage suppression lists, and perform ongoing hygiene based on delivery events.
  • Operational reliability: Use idempotency keys, retry/backoff strategies, timeouts, and queueing patterns for production-grade sending.
  • Webhooks & event handling: Set up signed webhooks, deduplicate events, and update suppression/sending decisions based on bounce and complaint outcomes.

Quick Start

Tell me how to fix my transactional emails going to spam in Gmail by implementing SPF/DKIM/DMARC, verifying DNS records, adding List-Unsubscribe, improving sender reputation, and setting up webhook-driven suppression.

Frequently Asked Questions about email-best-practices

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

FAQPage Schema
How do I stop my transactional emails going to the spam folder in Gmail?

To stop transactional emails going to spam in Gmail, implement SPF, DKIM, and DMARC authentication, verify your DNS records, add a List-Unsubscribe header, and set up webhook-driven suppression lists based on bounce and complaint events.

What is the best way to implement SPF, DKIM, and DMARC for email deliverability?

The best way to implement SPF, DKIM, and DMARC for email deliverability is to follow a phased rollout plan that updates DNS records, authenticates sending domains, and monitors aggregate reports to enforce DMARC policies while warming up your sending IP.

How do I manage email list hygiene and suppressions after webhook bounce events?

Manage email list hygiene by processing webhook events to automatically deduplicate bounces and complaints, then update your suppression lists and retention rules based on ongoing delivery outcomes to maintain sender reputation.

Do I need double opt-in to meet GDPR and CASL email compliance requirements?

GDPR and CASL compliance requires explicit consent and verifiable records, making double opt-in a reliable mechanism to validate email addresses and document subscriber permission for both marketing and transactional use cases.

How does idempotency and retry backoff work for production-grade email sending?

Idempotency keys and retry backoff strategies ensure production-grade email sending reliability by preventing duplicate message delivery during network timeouts and safely re-queuing failed requests without exceeding rate limits.

When should I separate sending infrastructure for marketing vs transactional emails?

You should separate sending infrastructure for marketing versus transactional emails to isolate sender reputation, preventing marketing complaint rates from negatively impacting the deliverability of critical transactional messages.