email-infra-bounce-auditlisted

Audit a bounce or blacklist problem to root cause and produce a full bounce report. Use for pulling replies via the EmailBison MCP/API, working around the broken type=bounced filter, stripping auto-replies, classifying bounces (Hard/Soft/Block) by SMTP/DSN code, running the neutral-copy test, and tracing the cause to infrastructure, list/data, or copy. Triggers on bounce audit, why are my emails bouncing, blacklist, Spamhaus, URIBL, hard bounce, soft bounce, block bounce, SMTP codes, DSN codes, bounce report, deliverability drop. Do NOT use for reading the health dashboard (use the dashboard-reading sub-skill) or list verification (use gt-list-building).
Growth-Today/claude-skills · ★ 3 · AI & Automation · score 71

Install: claude install-skill Growth-Today/claude-skills

# Blacklist & Bounce Audit · [GTM Engineer] > **Reads:** `{SKILL_BASE}/resources/reference.md` §7 · **Tools:** the **Instantly MCP** (`list_accounts`, `analytics_campaign_overview`, `list_emails`) for the live platform, and the EmailBison **REST API** (`/accounts`, `/campaigns`, `/campaigns/{id}/replies`) for campaigns still finishing there · optional Notion MCP · **Related:** dashboard-reading, domain-research · gt-list-building. > **These are REST endpoints, not MCP tools.** There is no EmailBison MCP connector today, so > `curl` is the primary path on this page, not the 50K+ fallback. The Instantly MCP *is* connected > and covers the same ground for an Instantly workspace — `list_accounts`, `list_campaigns`, > `list_emails` — but the field names differ, so don't paste a Bison field into an Instantly call. Find where a bounce or blacklist problem *actually* comes from, then produce a report the team can act on. The output is a clear root cause, **infrastructure, list/data, or copy**, plus a full bounce breakdown and the right owner. Runs on any EmailBison workspace (specify the MCP server / API host). Codes and thresholds in `{SKILL_BASE}/resources/reference.md` §7. **When to run:** monthly/quarterly check-in · bounce rate crosses 3% · before scaling send volume · a client asks "why are my emails bouncing?" · after onboarding new domains/inboxes. **Ask if not provided:** which **EmailBison MCP server / API host** (the workspace), **output location** for the CSV + repor