email-infra-campaign-buildinglisted
Install: claude install-skill Growth-Today/claude-skills
# Campaign Building & ESP/SEG Routing · [GTM Engineer]
> **Reads:** `{SKILL_BASE}/resources/reference.md` §1, §2, §7, §8 · **Related:** dashboard-reading, bounce-audit · gt-list-building.
> 🔒 **Read-only area.** The campaign build and the routing are done from the **email infra management system**, not by hand in the sequencer. Use this sub-skill to decide *what* the campaign and routing should be, read the live config to check it, and report the gap. Do not edit a campaign or a routing rule in Instantly / EmailBison / Smartlead / Lemlist directly — that creates a second source of truth. The `--esp-mix` profiling below is read-only and safe to run.
How to build a campaign that routes to the right inboxes and gets optimized from data, not from a 2024 rule of thumb. Numbers and taxonomy live in `{SKILL_BASE}/resources/reference.md` §1, §2, §8.
You are not A/B-testing copy. You are reading a **matrix of already-segmented sends** and pushing volume toward what works. The winning combination is `lead list × sending vendor/ESP × recipient ESP × SEG`, and it's on the dashboard.
---
### Determining the recipient ESP mix on a lead list
**Fastest path — run the playbook, no Clay credits:**
```bash
cd {SKILL_BASE}/playbooks/dns-auth-audit/scripts
uv run execute.py --esp-mix --file lead_domains.txt --csv acme_esp_mix.csv
```
Queries MX directly and prints the distribution, the SEG share, and a `no-email`
count (domains with no MX at all — guaranteed hard bounces, strip them befo