Email Systems

Email might return $36 for every $1 spent, but most startups still blast everyone on the same shared IP and wonder why password resets land in spam. This walks you through the infrastructure decisions that actually matter: separating transactional from marketing sends, getting SPF/DKIM/DMARC records right before launch, processing bounce webhooks so dead addresses don't tank your reputation, and building preference centers that keep you legal. The React Email patterns and queue-based retry logic are solid starting points. If you're about to pick an email provider or debug why your open rates are dismal, the sharp edges section on authentication records and shared IP risks will save you weeks.

skills.sh installs: 616
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill email-systems --agent claude-code

Installs into .claude/skills of the current project.

Files

Email Systems

Measure email return and deliverability for the actual audience and attribution window; no universal ROI or inbox-delivery guarantee applies.

This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

Use this skill when the request clearly matches the capabilities and patterns described above.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.