4a5f1234bb
* chore: upgrade maintenance scripts to robust PyYAML parsing - Replaces fragile regex frontmatter parsing with PyYAML/yaml library - Ensures multi-line descriptions and complex characters are handled safely - Normalizes quoting and field ordering across all maintenance scripts - Updates validator to strictly enforce description quality * fix: restore and refine truncated skill descriptions - Recovered 223+ truncated descriptions from git history (6.5.0 regression) - Refined long descriptions into concise, complete sentences (<200 chars) - Added missing descriptions for brainstorming and orchestration skills - Manually fixed imagen skill description - Resolved dangling links in competitor-alternatives skill * chore: sync generated registry files and document fixes - Regenerated skills index with normalized forward-slash paths - Updated README and CATALOG to reflect restored descriptions - Documented restoration and script improvements in CHANGELOG.md * fix: restore missing skill and align metadata for full 955 count - Renamed SKILL.MD to SKILL.md in andruia-skill-smith to ensure indexing - Fixed risk level and missing section in andruia-skill-smith - Synchronized all registry files for final 955 skill count * chore(scripts): add cross-platform runners and hermetic test orchestration * fix(scripts): harden utf-8 output and clone target writeability * fix(skills): add missing date metadata for strict validation * chore(index): sync generated metadata dates * fix(catalog): normalize skill paths to prevent CI drift * chore: sync generated registry files * fix: enforce LF line endings for generated registry files
60 lines
2.1 KiB
Markdown
60 lines
2.1 KiB
Markdown
---
|
|
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 cov...
|
|
risk: unknown
|
|
source: vibeship-spawner-skills (Apache 2.0)
|
|
date_added: '2026-02-27'
|
|
---
|
|
|
|
# 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: |
|
|
|
|
## When to Use
|
|
This skill is applicable to execute the workflow or actions described in the overview.
|