outreach-deliverability

# Deliverability audit and launch gate ## What this does Checks whether the mailboxes and domains you are about to send from can carry the campaign, and refuses the launch when they cannot. It reads the DNS records with `dig`, the warmup and health of every mailbox from Emelia, and the volume you are planning, then writes one verdict and a ramp plan to `outreach/deliverability.md`. It is the step that saves the domain. A burnt domain is not repaired by better copy. ## When to use it Run it before every launch. `outreach-campaign` reads its verdict and stops when the verdict is BLOCKED, so run this first, not after. Run it again when opens collapse, when replies stop, when a mailbox stops sending, when you add a mailbox or a domain, or before raising the daily volume. Use a different skill when the question is not infrastructure: `outreach-verify` checks whether the addresses on your list exist, `outreach-write` checks the copy for spam patterns and subject length, `outreach-audit` tells you whether a low reply rate is deliverability or the offer. ## Inputs - **The sending domains.** Take them from the mailboxes returned by Emelia. If Emelia is not connected, ask the user for the list of sending addresses and work from the part after the `@`. - **`EMELIA_API_KEY`** in the environment, or the Emelia MCP server configured. Without either, do the DNS half and report the warmup half as `unknown`, never as OK. - **`dig`**, part of `bind-utils` or `dnsutils`. If it is ...