Update to ACA

{
  "description": "Review ACA email infrastructure readiness. Use when the user asks about domain setup, BYO email infrastructure, mailbox provisioning, DNS readiness (SPF, DKIM, DMARC), warmup readiness, or whether email infra is ready for cold outreach.",
  "included_files": [],
  "name": "aca-email-infra-readiness",
  "skill_md_contents": "---\nname: aca-email-infra-readiness\ndescription: \"Review ACA email infrastructure readiness. Use when the user asks about domain setup, BYO email infrastructure, mailbox provisioning, DNS readiness (SPF, DKIM, DMARC), warmup readiness, or whether email infra is ready for cold outreach.\"\nlicense: MIT\ncompatibility: Requires the ACA connector (OAuth sign-in, no API key).\nmetadata:\n  author: ACA\n  version: \"1.1\"\n  homepage: https://www.automatedclientacquisition.com/mcp\n---\n\n# ACA email infrastructure readiness\n\nReview whether the email foundation (domains, DNS, mailboxes, warmup, capacity) is ready before sequences scale. The connector reports only the mailbox count; domains, DNS, warmup and mailbox state come from the user, public DNS, or the ACA app.\n\n## Rules\n\n- Use the ACA connector only. Never ask for vendor API keys or run SQL/API calls.\n- Be clear when a fix happens at the DNS provider or in the ACA app rather than through the connector.\n- Never claim SPF, DKIM or DMARC status you have not seen. Use records the user pastes or a public DNS lookup you actually ran.\n- Never invent warmup progress or health scores.\n- Prefer a readiness checklist over speculative diagnosis.\n- The connection is bound to one workspace. To review another, the user switches their active workspace in ACA and reconnects.\n\n## Workflow\n\n### 1. Read the workspace\n\n- `get_started`: mailbox count and active campaign count.\n- `list_sequences`: how many sequences exist or are active, which sets the capacity needed.\n- `list_campaigns`: active campaigns that may share senders.\n\nIf `get_started` is not available, use `get_workspace` plus the `list_*` tools above.\n\n### 2. Gather infrastructure details\n\nAsk in one message for what the connector does not expose:\n\n- Sending domains, and whether they are separate from the main company domain\n- Mailbox provider (Google Workspace, Microsoft 365, BYO SMTP) and mailboxes per domain\n- Mailbox ages and warmup start dates, as shown at `/email/mailboxes`\n- Planned daily volume\n\n### 3. Check DNS per sending domain\n\nRun a public DNS lookup if your tools allow it; otherwise ask the user to paste the records.\n\n- **MX**: present and pointing at the mailbox provider.\n- **SPF**: exactly one `v=spf1` TXT record, includes the provider, ends in `~all` or `-all`, under 10 DNS lookups.\n- **DKIM**: provider selector published and signing enabled in the provider admin.\n- **DMARC**: `_dmarc` TXT record exists; `p=none` with a `rua` address is a fine start, move to `quarantine` once stable.\n- **Custom tracking domain** (if tracking is used): CNAME set, HTTPS working.\n- **Domain redirect**: sending domains redirect to the main website.\n\n### 4. Check capacity and warmup\n\n- Mailboxes: 2 to 3 per sending domain; do not put many mailboxes on one domain.\n- Warmup: 2 to 3 weeks before cold sends; keep warmup running alongside cold sends.\n- Capacity: roughly 30 to 50 cold emails per mailbox per day. Planned daily volume divided by that gives the mailboxes needed; if the count from `get_started` is short, say how many more are needed.\n- New domains: register 2 to 4 weeks ahead of launch where possible.\n\n### 5. Produce the checklist and route\n\nMark each item ready, caution, or not ready, and say where it gets fixed: the DNS provider, the mailbox provider, or `/email/mailboxes`.\n\n## Output format\n\n```text\nEmail infra readiness: {ready/caution/not ready}\n\nKnown from ACA:\n- Mailboxes: {count from get_started}\n- Sequences/campaigns needing capacity: {counts}\n\nChecked (DNS / user-provided):\n- {domain}: MX {ok/missing}, SPF {ok/issue}, DKIM {ok/issue}, DMARC {ok/issue}\n\nNeeds a check in the app or DNS:\n- {item} → {where}\n\nCapacity: {mailboxes needed} vs {mailboxes connected}\nNext: {skill/action}\n```\n\n## Skill chaining\n\nPreserve the workspace, relevant IDs, the user's brief, approval state, and the domain checklist when continuing into another ACA skill.\n\n**Upstream**\n- Called by `aca-sender-health`, `aca-email-deliverability-audit`, or setup workflows.\n\n**Auto-continue conditions**\n- Mailboxes exist: continue to `aca-sender-health`.\n- Infrastructure looks ready but cold-email risk is unknown: continue to `aca-email-deliverability-audit`.\n- A small proof is needed: continue to `aca-deliverability-test`.\n\n**Stop before chaining when**\n- DNS, mailbox provider or ACA app actions are required. Tell the user exactly what to set and where.\n\n**Downstream skills**\n- `aca-sender-health`: check connected sender state.\n- `aca-email-deliverability-audit`: audit sequence readiness.\n- `aca-deliverability-test`: verify with a controlled preflight.\n\n**Handoff block**\n\n```text\nChain state: {continue|needs_approval|blocked|complete}\nNext skill: {aca-skill-name|none}\nReason: {why}\nCarry forward: {workspace, sending domains, DNS status, mailbox count, capacity gap, approvals, constraints}\n```\n\n## ACA tools used\n\n- `get_started`, `get_workspace`\n- `list_sequences`\n- `list_campaigns`\n\n## ACA app pages\n\n- Connect and manage mailboxes, warmup, limits: `https://www.automatedclientacquisition.com/email/mailboxes`\n- Sending results once live: `https://www.automatedclientacquisition.com/email/analytics`\n"
}