# Build Reliable Email Systems

Email systems often fail through weak deliverability, missing consent controls, or unreliable sending. This skill provides patterns for dependable transactional and marketing email infrastructure.

## Install

```bash
npx skillstore add sickn33/email-systems
```

## Metadata

- Status: approved
- Slug: sickn33-email-systems
- Skillstore revision: r2
- Version status: missing
- Tree hash: 782db7557c5f4a691bf6491b1a332d2d7a4ad6ff2399321aaf41d910b34e3d61
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/email-systems
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-email-systems
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-email-systems/manifest

## Capabilities

- Design queued transactional email delivery with retries and monitoring.
- Separate transactional and marketing traffic to protect deliverability.
- Plan SPF, DKIM, DMARC, and IP warm-up practices.
- Handle bounces, complaints, unsubscribes, and recipient preferences.
- Create accessible multipart email and React Email templates.
- Track campaign outcomes and recover from partial send failures.

## Use Cases

- Launch Transactional Email: Plan reliable password resets, receipts, confirmations, queues, retries, and bounce processing.
- Improve Campaign Deliverability: Review authentication, consent, list hygiene, warm-up, unsubscribe, and monitoring practices.
- Audit Email Architecture: Identify reliability, accessibility, compliance, and reputation risks across an existing email system.

## Prompt Templates

### Review One Email Flow

```
Review this email flow: [describe flow]. Identify reliability, deliverability, consent, and accessibility gaps. Recommend the three highest-priority improvements.
```

### Design Transactional Delivery

```
Design a transactional email system for [product]. Include provider separation, queue behavior, retries, idempotency, authenticated webhooks, bounce handling, and monitoring.
```

### Plan Marketing Operations

```
Create an email operations plan for [audience and volume]. Cover consent, segmentation, preferences, authentication, warm-up, rate limits, complaints, and success metrics.
```

### Audit a Production System

```
Audit this email architecture: [details]. Build a prioritized risk register covering security, deliverability, privacy, reliability, recovery, observability, and provider dependencies.
```

## Limitations

- It does not configure DNS records, providers, queues, or production infrastructure.
- Code examples require adaptation, authentication, validation, and testing before production use.
- Legal requirements vary by region and require qualified review.
- Provider-specific limits, pricing, APIs, and deliverability policies may change.

## Best Practices

- Separate critical transactional messages from marketing traffic and reputation.
- Authenticate domains and provider webhooks before processing production email events.
- Monitor each send, suppress hard bounces, and honor complaints or unsubscribes immediately.

## Anti Patterns

- Do not send marketing email to purchased, scraped, or unconsented contacts.
- Do not send large volumes from a new domain or IP without gradual warm-up.
- Do not trust webhook payloads or update recipient state without signature verification.

## Security Audit

- Audited at: 2026-07-23T23:21:36.674\+00:00
- Summary: All 24 static detections are false positives caused by Markdown fences, placeholder URLs, or defensive email guidance. A separate high-severity issue remains: the bounce webhook example trusts an unsigned request body, enabling forged suppression events if implemented directly.

## Stats

- Views: 112
- Downloads: 12
- Favorites: 0
- Popularity score: 0