# Aca Email Deliverability Audit

> Audit ACA cold email readiness before launch. Use when the user asks about deliverability, inbox placement, warmup, mailbox health, sending limits, bounce risk, or whether a sequence is safe to start.

- Skill: `seguelacedric/aca-email-deliverability-audit` (Agent Skill)
- Install (CLI): `npx skillmds@latest add seguelacedric/aca-email-deliverability-audit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/seguelacedric/aca-email-deliverability-audit/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: seguelaCedric (https://skillmd.com/u/seguelacedric)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/seguelacedric/aca-email-deliverability-audit

---


# ACA email deliverability audit

Review whether ACA email outreach is ready to send without unnecessary risk.

## Rules

- Read-only unless the user explicitly approves changes.
- Do not promise inbox placement. Report risk levels and concrete blockers.
- Treat disconnected mailboxes, high bounce risk lists, aggressive volume, and spammy copy as blockers.

## Workflow

1. Inspect `list_email_mailboxes`, `list_sender_accounts` with `channel: "email"`, `list_email_sequences`, and active email campaigns from `list_campaigns`.
2. For relevant sequences, call `get_email_sequence`.
3. Review:
   - Connected mailbox count
   - Warmup and reputation fields if returned
   - Daily limits and send windows
   - Step count and spacing
   - Tracking settings
   - Lead list quality and email status
   - Copy risk using `aca-copy-spam-checker`
4. Report blockers, warnings, and launch-safe defaults.

## Output format

```text
Deliverability audit: {pass / caution / blocked}

Blockers:
- {blocker}

Warnings:
- {warning}

Recommended limits:
- Daily new leads: {n}
- Gap: {minutes}
- Tracking: {recommendation}
```

## Skill chaining

This skill participates in the ACA chain. Preserve the selected ACA org, relevant IDs, user brief, approval state, and any generated artifacts when continuing into another ACA skill. If the user asked for execution and a downstream condition is met, continue into the next skill automatically; otherwise end with the handoff block.

**Upstream**
- Called by `aca-launch-outreach`, `aca-sender-health`, `aca-email-sequence-manager`, or incident workflows.

**Auto-continue conditions**
- Infrastructure is not ready -> continue to `aca-email-infra-readiness`.
- Copy risk exists -> continue to `aca-copy-spam-checker`.
- A controlled test is needed -> continue to `aca-deliverability-test`.
- Audit passes and campaign is queued -> continue to `aca-launch-outreach`.

**Stop before chaining when**
- Ask before sequence/campaign changes.

**Downstream skills**
- `aca-email-infra-readiness` - fix readiness gaps.
- `aca-copy-spam-checker` - reduce copy risk.
- `aca-deliverability-test` - run small preflight.
- `aca-launch-outreach` - launch after passing.

**Handoff block**

```text
Chain state: {continue|needs_approval|blocked|complete}
Next skill: {aca-skill-name|none}
Reason: {why this handoff is or is not needed}
Carry forward: {org_id/name, product_id, icp_id, lead_list_id, campaign_id, sequence_id, job_id, approvals, constraints}
```

## ACA tools used

- `list_email_mailboxes`
- `list_sender_accounts`
- `list_email_sequences`, `get_email_sequence`
- `list_campaigns`, `get_campaign`
- `get_lead_list`