email-service

Design transactional email platforms with SMTP, SPF/DKIM/DMARC, and bounce handling architecture.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/hung-phan/system-skills --skill email-service-hung-phan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-service
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/interview-templates/email-service
Command: npx skills add https://github.com/hung-phan/system-skills --skill email-service-hung-phan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you design and optimize transactional and marketing email platforms, addressing deliverability challenges, reputation management, and architectural best practices.

Core Features & Use Cases

  • Email Platform Design: Guidance on creating a robust email platform architecture.
  • Reputation Management: Strategies for maintaining a strong sender reputation.
  • Deliverability: Best practices for ensuring high email delivery rates.
  • Use Case: When designing a new email service, use this Skill to understand how to separate transactional and marketing emails to avoid reputation damage.

Quick Start

Use the email-service skill to design a transactional email platform that handles high volumes and maintains a strong deliverability rate.

Frequently Asked Questions about email-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate transactional and marketing emails to protect sender reputation?

To protect sender reputation, you should separate transactional and marketing emails by splitting your delivery pipelines. This architectural best practice prevents marketing email bounce rates from damaging the deliverability of critical transactional messages.

What is IP warming and when do I need it for SMTP email deliverability?

IP warming is the process of gradually increasing email volume sent over a new SMTP IP address to build a positive sender reputation. You need it when launching a new email platform to ensure high deliverability rates and avoid spam filtering.

How does bounce handling affect email platform deliverability and reputation management?

Bounce handling directly affects deliverability and reputation management by identifying invalid recipients and stopping sends to them. Properly processing bounce responses prevents spam traps from triggering and maintains your platform's sender reputation.

Do I need to configure SPF, DKIM, and DMARC for a transactional email platform?

Yes, you need to configure SPF, DKIM, and DMARC for a transactional email platform to authenticate SMTP sends. These protocols verify domain ownership, prevent email spoofing, and are critical for maintaining high deliverability rates.

What's the best way to design an email platform architecture for high volume sending?

The best way to design a high volume email platform architecture is to implement pipeline splitting, robust bounce handling, and dedicated IP warming strategies. This ensures optimal deliverability while maintaining strong sender reputation management across SMTP streams.

Why does my email deliverability drop when sending marketing and transactional emails together?

Email deliverability drops when sending marketing and transactional emails together because marketing campaigns often generate higher bounce and complaint rates. Shared IP or domain reputation causes your critical transactional emails to be filtered as spam.