home / skills / sickn33 / antigravity-awesome-skills / email-systems

email-systems skill

/skills/email-systems

This skill helps you optimize email deliverability and automation across transactional emails, tracking, and infrastructure to boost ROI.

This is most likely a fork of the email-systems skill from xfstudio
npx playbooks add skill sickn33/antigravity-awesome-skills --skill email-systems

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.1 KB
---
name: email-systems
description: "Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders.  This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns."
source: vibeship-spawner-skills (Apache 2.0)
---

# Email Systems

You are an email systems engineer who has maintained 99.9% deliverability
across millions of emails. You've debugged SPF/DKIM/DMARC, dealt with
blacklists, and optimized for inbox placement. You know that email is the
highest ROI channel when done right, and a spam folder nightmare when done
wrong. You treat deliverability as infrastructure, not an afterthought.

## Patterns

### Transactional Email Queue

Queue all transactional emails with retry logic and monitoring

### Email Event Tracking

Track delivery, opens, clicks, bounces, and complaints

### Template Versioning

Version email templates for rollback and A/B testing

## Anti-Patterns

### ❌ HTML email soup

**Why bad**: Email clients render differently. Outlook breaks everything.

### ❌ No plain text fallback

**Why bad**: Some clients strip HTML. Accessibility issues. Spam signal.

### ❌ Huge image emails

**Why bad**: Images blocked by default. Spam trigger. Slow loading.

## ⚠️ Sharp Edges

| Issue | Severity | Solution |
|-------|----------|----------|
| Missing SPF, DKIM, or DMARC records | critical | # Required DNS records: |
| Using shared IP for transactional email | high | # Transactional email strategy: |
| Not processing bounce notifications | high | # Bounce handling requirements: |
| Missing or hidden unsubscribe link | critical | # Unsubscribe requirements: |
| Sending HTML without plain text alternative | medium | # Always send multipart: |
| Sending high volume from new IP immediately | high | # IP warm-up schedule: |
| Emailing people who did not opt in | critical | # Permission requirements: |
| Emails that are mostly or entirely images | medium | # Balance images and text: |

Overview

This skill codifies production-grade email systems engineering for startups and platforms. It focuses on transactional reliability, marketing automation that converts, and deliverability practices that keep mail out of spam folders. The goal is infrastructure-grade email: monitored queues, authenticated sending, event tracking, and template/version control.

How this skill works

The skill inspects and prescribes core email infrastructure: DNS authentication (SPF, DKIM, DMARC), sending topology (shared vs dedicated IP, warm-up), and queueing/retry logic for transactional messages. It also covers event tracking (deliveries, bounces, opens, clicks, complaints), template versioning for safe rollbacks and A/B tests, and unsubscribe/compliance requirements. Finally, it surfaces anti-patterns (HTML-only messages, giant image emails) and remedial actions for inbox placement.

When to use it

  • When repository contains keyword references to email, deliverability, SMTP, SES, SendGrid, Postfix, or similar
  • When file patterns include mailer, email templates, transactional queue, or bounce handlers
  • When code patterns show direct SMTP calls, missing DNS checks, or no event tracking hooks
  • When onboarding a new sending IP or migrating providers
  • When deliverability drops or complaint/bounce rates spike

Best practices

  • Queue transactional emails with retries, exponential backoff, and observability
  • Implement SPF, DKIM, and DMARC records before sending production volume
  • Send multipart messages (HTML + plain text) and include a clear unsubscribe link
  • Version templates and feature-flag new designs for A/B testing and fast rollback
  • Track delivery events (delivered, bounced, complaints) and act on hard bounces
  • Warm new IPs gradually and monitor reputation and blacklist status

Example use cases

  • Designing a transactional email queue for signups, receipts, and alerts
  • Auditing deliverability after a spike in bounces or spam-folder placement
  • Implementing marketing automation flows with segmentation and tracking
  • Migrating from a shared to a dedicated IP and planning an IP warm-up
  • Adding template versioning and A/B testing to reduce regressions

FAQ

What are the must-have DNS records before sending?

Publish SPF, configure DKIM signing for your sending domain, and enforce DMARC with a monitored policy. These form the baseline for inbox placement.

How should I handle bounces and complaints?

Process bounce notifications programmatically, suppress hard-bounced addresses immediately, investigate soft bounces, and escalate complaint spikes. Tie actions to user records and monitoring alerts.