Aca Deliverability Test

---
name: aca-deliverability-test
description: "Plan and run a controlled ACA email preflight test. Use before launching a new sequence, new mailbox, new domain, or high-volume campaign."
license: MIT
compatibility: Requires the ACA MCP server connected with a valid bearer token. Sending changes require approval.
metadata:
  author: ACA
  version: "1.0"
  homepage: https://aca.so/product/campaigns
---

# ACA deliverability test

Create a low-risk preflight plan for email sending.

## Rules

- Do not send test traffic without approval.
- Keep tests small.
- Test infrastructure, copy, tracking, and enrollment separately where possible.

## Workflow

1. Inspect `list_email_mailboxes`, `list_email_sequences`, `list_sender_accounts`, and `list_lead_lists`.
2. Choose the asset to test: mailbox, sequence, campaign, or list.
3. Review copy with `aca-copy-spam-checker`.
4. Build a test plan:
   - Test list size
   - Mailboxes included
   - Daily cap
   - Send window
   - Pass/fail criteria
5. If approved, create or update a draft sequence with `create_email_sequence` or `update_email_sequence`, enroll test leads with `enroll_leads`, and activate with `toggle_email_sequence`.
6. Record the test plan with `create_strategy_document`.

## Output format

```text
Deliverability test plan:
Asset: {sequence/campaign/mailbox}
Sample size: {n}
Mailboxes: {mailboxes}
Pass criteria: {criteria}
Risk: {low/medium/high}
Approval needed before sending: yes
```

## 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-email-deliverability-audit`, `aca-email-infra-readiness`, or before a high-risk launch.

**Auto-continue conditions**
- Test plan needs a sequence -> continue to `aca-email-sequence-manager`.
- Test passes and campaign exists -> continue to `aca-launch-outreach`.
- Test fails -> continue to `aca-deliverability-incident-response`.

**Stop before chaining when**
- Ask before sending test traffic.

**Downstream skills**
- `aca-email-sequence-manager` - create/enroll test sequence.
- `aca-launch-outreach` - proceed after passing.
- `aca-deliverability-incident-response` - triage failures.

**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`, `create_email_sequence`, `update_email_sequence`, `toggle_email_sequence`, `enroll_leads`
- `list_lead_lists`, `get_lead_list`
- `create_strategy_document`