email-systems
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.
Best use case
email-systems is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using email-systems should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/email-systems/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How email-systems Compares
| Feature / Agent | email-systems | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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: |
Related Skills
email-triage-draft-replies
Review unread email, categorize it, and draft replies (no sending without approval)
email-extractor
Expert in email content extraction and analysis. **Use whenever the user mentions .eml files, email messages, says "Extract email information", "Using the email information", or requests to extract, parse, analyze, or process email files.** Handles email thread parsing, attachment extraction, and converting emails to structured markdown format for AI processing. (project, gitignored)
agent-memory-systems
Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm
agent-embedded-systems
Expert embedded systems engineer specializing in microcontroller programming, RTOS development, and hardware optimization. Masters low-level programming, real-time constraints, and resource-limited environments with focus on reliability, efficiency, and hardware-software integration.
verifiedemail-automation
Automate Verifiedemail tasks via Rube MCP (Composio). Always search tools first for current schemas.
jikime-marketing-email
Email marketing and automation specialist for creating email sequences, drip campaigns, lifecycle emails, and nurture flows.
google-email
Manage Gmail email sync, triage, and analysis workflows. Use when user wants to sync emails, triage inbox, check email analysis results, view email statistics, manage the email processing pipeline, find newsletters, check pending emails, or understand email workflow status. Triggers on phrases like "sync my emails", "triage inbox", "email status", "check newsletters", "email analysis", "what emails do I have", "pending emails", "unsubscribe from newsletters".
enginemailer-automation
Automate Enginemailer tasks via Rube MCP (Composio). Always search tools first for current schemas.
emailoctopus-automation
Automate Emailoctopus tasks via Rube MCP (Composio). Always search tools first for current schemas.
emaillistverify-automation
Automate Emaillistverify tasks via Rube MCP (Composio). Always search tools first for current schemas.
emailable-automation
Automate Emailable tasks via Rube MCP (Composio). Always search tools first for current schemas.
email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.