ACA deliverability incident response
Diagnose sending incidents and propose the smallest safe intervention.
Rules
- Start read-only.
- Pause campaigns or sequences only after approval.
- Preserve evidence: name the campaign, sequence, mailbox, and symptom.
- Do not retry aggressively after failures.
Workflow
- Inspect
list_email_mailboxes, list_sender_accounts, list_email_sequences, and list_campaigns.
- For affected assets, call
get_email_sequence, list_email_enrollments, get_campaign, and list_campaign_leads where relevant.
- Classify the incident:
- Mailbox disconnected
- Reputation/warmup issue
- Bounce spike
- Bad list quality
- Copy/content issue
- Volume/rate issue
- Processor/campaign stalled
- Recommend actions in order: pause, reduce volume, clean list, rewrite copy, reconnect sender, or split traffic.
- If approved, use
toggle_email_sequence, update_campaign_status, or update_email_sequence.
- Save the incident note with
create_strategy_document.
Output format
Incident: {summary}
Severity: {low / medium / high}
Likely cause: {cause}
Evidence: {evidence}
Recommended action: {action}
Approval needed: {yes/no}
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-pipeline-status, aca-weekly-rhythm, aca-deliverability-test, or user-reported failures.
Auto-continue conditions
- Sender issue -> continue to
aca-sender-health.
- Copy issue -> continue to
aca-copy-spam-checker.
- List issue -> continue to
aca-lead-quality.
- Reply quality issue -> continue to
aca-positive-reply-scoring.
Stop before chaining when
- Ask before pausing campaigns/sequences or changing limits.
Downstream skills
aca-sender-health - inspect accounts/mailboxes.aca-copy-spam-checker - fix risky copy.aca-lead-quality - clean bad lists.aca-positive-reply-scoring - separate deliverability from market response.aca-weekly-rhythm - record incident follow-up.
Handoff block
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_accountslist_email_sequences, get_email_sequence, list_email_enrollments, toggle_email_sequence, update_email_sequencelist_campaigns, get_campaign, list_campaign_leads, update_campaign_statuscreate_strategy_document
1---2name: aca-deliverability-incident-response3description: Triage ACA email deliverability incidents. Use when the user reports bounces, spam placement, failed sends, reputation drops, disconnected mailboxes, throttling, or campaigns that suddenly stopped sending.4license: MIT5---67# ACA deliverability incident response89Diagnose sending incidents and propose the smallest safe intervention.1011## Rules1213- Start read-only.14- Pause campaigns or sequences only after approval.15- Preserve evidence: name the campaign, sequence, mailbox, and symptom.16- Do not retry aggressively after failures.1718## Workflow19201. Inspect `list_email_mailboxes`, `list_sender_accounts`, `list_email_sequences`, and `list_campaigns`.212. For affected assets, call `get_email_sequence`, `list_email_enrollments`, `get_campaign`, and `list_campaign_leads` where relevant.223. Classify the incident:23 - Mailbox disconnected24 - Reputation/warmup issue25 - Bounce spike26 - Bad list quality27 - Copy/content issue28 - Volume/rate issue29 - Processor/campaign stalled304. Recommend actions in order: pause, reduce volume, clean list, rewrite copy, reconnect sender, or split traffic.315. If approved, use `toggle_email_sequence`, `update_campaign_status`, or `update_email_sequence`.326. Save the incident note with `create_strategy_document`.3334## Output format3536```text37Incident: {summary}38Severity: {low / medium / high}39Likely cause: {cause}40Evidence: {evidence}41Recommended action: {action}42Approval needed: {yes/no}43```4445## Skill chaining4647This 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.4849**Upstream**50- Called by `aca-pipeline-status`, `aca-weekly-rhythm`, `aca-deliverability-test`, or user-reported failures.5152**Auto-continue conditions**53- Sender issue -> continue to `aca-sender-health`.54- Copy issue -> continue to `aca-copy-spam-checker`.55- List issue -> continue to `aca-lead-quality`.56- Reply quality issue -> continue to `aca-positive-reply-scoring`.5758**Stop before chaining when**59- Ask before pausing campaigns/sequences or changing limits.6061**Downstream skills**62- `aca-sender-health` - inspect accounts/mailboxes.63- `aca-copy-spam-checker` - fix risky copy.64- `aca-lead-quality` - clean bad lists.65- `aca-positive-reply-scoring` - separate deliverability from market response.66- `aca-weekly-rhythm` - record incident follow-up.6768**Handoff block**6970```text71Chain state: {continue|needs_approval|blocked|complete}72Next skill: {aca-skill-name|none}73Reason: {why this handoff is or is not needed}74Carry forward: {org_id/name, product_id, icp_id, lead_list_id, campaign_id, sequence_id, job_id, approvals, constraints}75```7677## ACA tools used7879- `list_email_mailboxes`, `list_sender_accounts`80- `list_email_sequences`, `get_email_sequence`, `list_email_enrollments`, `toggle_email_sequence`, `update_email_sequence`81- `list_campaigns`, `get_campaign`, `list_campaign_leads`, `update_campaign_status`82- `create_strategy_document`
seguelaCedric