Systems Lab

Agent skill

email-infra

Complete cold email infrastructure setup, DNS configuration, warmup, and troubleshooting.

slowingReaches the webInstructions only399 words

Filed under Outbound email.

From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14

What it does when it runs

Complete cold email infrastructure setup, DNS configuration, warmup, and troubleshooting. Use when the user asks about email infrastructure setup, domain purchasing for cold email, DNS configuration, MX/SPF/DKIM/DMARC setup, email warmup, mailbox provisioning, Google Workspace or Microsoft 365 for cold email, Instantly setup, going live with campaigns, deliverability monitoring, email blacklist recovery, warm-up troubleshooting, or scaling email infrastructure. Triggers on "email infra", "setup domains", "buy domains", "DNS setup", "MX records", "SPF record", "DKIM", "DMARC", "warmup", "warm up", "Instantly setup", "mailbox setup", "Google Workspace cold email", "Microsoft 365 cold email", "domain warmup", "email blacklist", "deliverability issue", "scaling email", "how many domains", "how many mailboxes". Do NOT use for email copywriting (use copywriting or first-touch) or general deliverability concepts (handled by orchestrator).

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
  • frontal.so
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about email-infra

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills
git -C /tmp/outbound-skills sparse-checkout set "master-skills/cold-email/.claude/skills/email-infra"
mkdir -p ~/.claude/skills/email-infra
cp -R "/tmp/outbound-skills/master-skills/cold-email/.claude/skills/email-infra/." ~/.claude/skills/email-infra/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/cold-email/.claude/skills/email-infra/SKILL.md, which is licensed MIT (repository). 399 words, 9 headings.

Email Infrastructure

You help users set up, configure, and troubleshoot cold email infrastructure from zero to live campaigns.

Reference

Read these resources based on the user's question:

  • Complete setup guide: domains, DNS, warmup, monitoring → Read {SKILL_BASE}/resources/frameworks/email-infra/email-infra-guide.md
  • Step-by-step walkthroughs with video tutorials → Read {SKILL_BASE}/resources/frameworks/email-infra/email-infra-step-by-step.md
  • Diagnosis and recovery for DNS, connection, warmup, deliverability issues → Read {SKILL_BASE}/resources/frameworks/email-infra/email-infra-troubleshooting.md

Critical Rules (Never Break)

  1. Never use primary domain for cold outreach
  2. Max 2 mailboxes per domain
  3. One domain = one workspace (never mix)
  4. Use multiple registrars (no single point of failure)
  5. Warm up 2-3 weeks minimum before sending
  6. Never disable warm-up once campaigns running
  7. Start conservative, scale gradually

Infrastructure Sizing Formula

  • Monthly goal / 20 working days = daily volume
  • Daily volume / 20-25 per mailbox = mailboxes needed
  • Mailboxes x 1.5 (buffer) / 2 = domains needed
  • Provider split: 60% Google Workspace, 40% Microsoft 365

DNS (All 4 Records Required)

RecordPurpose
MXRoutes incoming email
SPFDeclares sending servers
DKIMDigital signature authentication
DMARCPolicy for SPF/DKIM failures

Warmup Timeline

  • Week 1: Foundation (no campaigns)
  • Week 2: Building (no campaigns)
  • Week 3: Ready (health scores 70%+, ideally 90%+)

Going Live Ramp Schedule

WeekGoogleMicrosoft
110-15/day5-10/day
2-315-20/day10-12/day
4+20-25/day12-15/day

Healthy Metrics

  • Open rate: 50%+
  • Reply rate: 2%+
  • Bounce rate: <3% (target <2%)
  • Spam rate: <0.1%
  • Deliverability score: >95%

Examples

Example 1: "I want to send 3,000 emails per month, how many domains do I need?" → Read email-infra-guide.md. Calculate: 150/day → 10-12 mailboxes → 5-6 domains. Split 60/40 Google/Microsoft.

Example 2: "My warm-up shows a red flame in Instantly" → Read email-infra-troubleshooting.md. Run "Test domain setup", verify all 4 DNS records, check domain age, request reactivation.

Example 3: "Walk me through setting up a new domain from scratch" → Read email-infra-step-by-step.md. Follow 9-step process: calculate needs → buy domain → Google/Microsoft setup → DNS → connect Instantly → warmup → go live → monitor.


Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what email-infra does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.