About email-systems
An email systems skill for engineers designing reliable email delivery. It covers queueing, event tracking, template versioning, and common deliverability risks.
Key features
- 01Transactional email queues with retries
- 02Delivery and engagement event tracking
- 03Template versioning for rollback and testing
- 04Guidance on authentication and bounce handling
Use cases
- 01Designing a transactional email pipeline
- 02Monitoring delivery, opens, clicks, and bounces
- 03Reviewing email practices for deliverability risks
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/email-systemsin Claude Code to confirm it loaded.
Details
From the project READMEEmail 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: |