email-best-practices

Guides implementation of deliverable, compliant transactional and marketing email systems.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/elcokiin/vibe-tribe --skill email-best-practices-elcokiin
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/elcokiin/vibe-tribe/tree/main/.agents/skills/email-best-practices
Command: npx skills add https://github.com/elcokiin/vibe-tribe --skill email-best-practices-elcokiin

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve? Building email features involves many failure points: messages landing in spam, missing DNS authentication, legal compliance violations, duplicate sends, and unhandled bounces. This Skill provides structured guidance covering the full email lifecycle so your emails reach inboxes and meet legal requirements. ## Core Features & Use Cases - Deliverability & Authentication: Set up SPF, DKIM, and DMARC records, warm up sending IPs, and diagnose why emails go to spam. - Transactional & Marketing Guidance: Design password resets, OTPs, order confirmations, and newsletters with correct subject lines, mobile-first layouts, and consent flows. - Production Reliability: Implement idempotency keys, exponential backoff retries, webhook signature verification, and suppression list management. - Use Case: You are adding a password reset flow to a SaaS app. The Skill routes you to the transactional email guide for content design, the deliverability guide for DNS setup, and the sending reliability guide for idempotent retry logic. ## Quick Start Ask the agent to help you set up email authentication and plan the transactional emails your app needs, and it will route to the right resource.

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 for my domain?โ–ผ

Add an SPF TXT record listing your sending servers, publish the DKIM TXT record provided by your email service, and create a DMARC record starting with p=none for monitoring. Verify each with dig TXT commands, then tighten DMARC toward quarantine and reject.

Why are my emails going to spam?โ–ผ

Check authentication first, since Gmail and Yahoo reject unauthenticated email. Then verify the List-Unsubscribe header, sender reputation and blacklist status, content quality, and sending patterns such as sudden volume spikes.

What is the difference between transactional and marketing emails?โ–ผ

Transactional emails facilitate a user-initiated action like password resets or receipts and can be sent without opt-in. Marketing emails are promotional, require explicit consent, and must include an unsubscribe mechanism under GDPR and CASL.

How do I prevent duplicate emails when retrying failed sends?โ–ผ

Send a deterministic idempotency key derived from the business event, such as order-confirm-{orderId}, with each request. Retries with the same key return the original response instead of sending again, and keys are typically cached for 24 hours.

Does GDPR require double opt-in for newsletters?โ–ผ

GDPR requires explicit, freely given opt-in consent, and double opt-in is the recommended way to prove it. It verifies the address, confirms intent, reduces complaints, and is effectively required in some regions like Germany.

How should I handle bounced and complained emails?โ–ผ

Suppress hard bounces and spam complaints immediately and permanently via webhook events. Retry soft bounces on a schedule and suppress after about three failures, keeping bounce rate under 2% and complaints under 0.05%.