Update to ACA

{
  "description": "Plan, write, and review ACA email sequences. Use when the user asks to create an email sequence, edit steps, enroll leads, pause or resume a sequence, inspect sequences, or replace Smartlead-style sequence operations with ACA native email. Reads existing sequences, writes paste-ready sequence copy, and hands building, enrollment, and on/off to the ACA app.",
  "included_files": [],
  "name": "aca-email-sequence-manager",
  "skill_md_contents": "---\nname: aca-email-sequence-manager\ndescription: \"Plan, write, and review ACA email sequences. Use when the user asks to create an email sequence, edit steps, enroll leads, pause or resume a sequence, inspect sequences, or replace Smartlead-style sequence operations with ACA native email. Reads existing sequences, writes paste-ready sequence copy, and hands building, enrollment, and on/off to the ACA app.\"\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 sequence manager\n\nWork with ACA's native email sequence engine. The connector can read sequences (name, status, step count). Creating, editing, enrolling, pausing, and resuming happen in the ACA app at `/email/sequences`, so this skill writes the full sequence in chat in a paste-ready format and gives the exact next click.\n\n## Rules\n\n- `add_contacts_to_list` can trigger the target list's existing enrichment, campaign enrollment, external outreach, and configured webhooks. Before adding contacts, review that list's automation settings at `/leads/lists` and confirm the intended contacts and side effects. If the connector cannot expose those settings, ask the user to verify them in ACA; do not assume a list write is draft-only.\n- Use the ACA connector only. Never ask for vendor API keys or run SQL/API calls.\n- Never say a sequence was created, edited, enrolled, paused, or resumed. Those actions are done by the user in the app.\n- Never invent prospects, emails, proof points, or metrics. Proof and claims come from the user.\n- Ask before adding contacts to ACA. Only add people the user supplied, with `bulk_create_contacts` (100 per call).\n- Use HTML paragraphs for email bodies. Keep spacing conservative (3 to 4 days between touches) unless the user asks otherwise.\n- The connection is bound to one workspace. If the user wants a different one, they switch their active workspace in ACA and reconnect.\n\n## Workflow\n\n### 1. Read the workspace\n\nCall `get_started`. Note `counts.mailboxes`, `counts.lead_lists`, and `counts.contacts`. If it is not available, call `get_workspace` and `list_lead_lists`.\n\nIf `mailboxes` is 0, stop and route to `aca-sender-health`: the user connects a mailbox at `/email/mailboxes` before any sequence can send.\n\n### 2. Inspect existing sequences\n\nCall `list_sequences` (filter by `status` if the user asked about active or paused ones). For a specific sequence, call `get_sequence` to confirm its name, status, and `step_count`.\n\nThe connector returns summaries, not step copy. If the user wants to edit or review existing copy, ask them to paste it.\n\n### 3. Write or revise the sequence\n\nWrite the sequence in chat as a numbered block the user can paste step by step into the builder:\n\n```text\nSequence: {name}\nGoal: {goal}\nAudience: {list or ICP}\n\nStep 1 - Email\nSubject: {subject}\nBody:\n<p>{paragraph}</p>\n<p>{paragraph}</p>\n\nStep 2 - Wait {n} days\n\nStep 3 - Email (reply in thread)\nBody:\n<p>{paragraph}</p>\n\nStep 4 - Condition: stop if replied\n\nStep 5 - Wait {n} days\n\nStep 6 - Email (breakup)\n...\n```\n\nStep types to use, matching the builder: Email, Delay, Condition, and A/B test where a real single-variable split is wanted (hand variant work to `aca-copy-variants`).\n\nDefaults that work:\n\n- 3 to 4 emails. First email under 90 words, follow-ups shorter.\n- Follow-ups reply in the same thread with a new angle, not \"just bumping this\".\n- One CTA per email, usually a soft question.\n- Merge variables only for fields the contacts actually have (check one with `get_contact`).\n\nRun the copy through `aca-copy-spam-checker` before handoff.\n\n### 4. Prepare the audience (optional)\n\nIf the user wants to enroll a list:\n\n- `list_lead_lists` and `get_lead_list` to confirm the list and its `lead_count`.\n- If the user pasted people who are not in ACA yet, confirm count and fields, then add them with `bulk_create_contacts` after approval, and put them on a list with `create_lead_list` and `add_contacts_to_list`.\n\n### 5. Hand off to the app\n\nGive the exact steps:\n\n1. Open `https://www.automatedclientacquisition.com/email/sequences`.\n2. Create the sequence (or open the existing one by name) and paste each step.\n3. Attach mailboxes.\n4. Enroll the lead list.\n5. Turn the sequence on, or pause/resume it, from the same page.\n\nFor deliverability after launch, point to `https://www.automatedclientacquisition.com/email/analytics`.\n\n## Output format\n\n```text\nEmail sequence: {name}\nExisting in ACA: {yes, id and status from list_sequences | no}\nSteps written: {n}\nMailboxes connected: {mailboxes}\nLead list: {list_name} ({lead_count})\n\nFinish in ACA:\n- Build, enroll, turn on: https://www.automatedclientacquisition.com/email/sequences\n```\n\n## Skill chaining\n\nPreserve the workspace, relevant IDs, the user's brief, approval state, and the written sequence when continuing into another ACA skill.\n\n**Upstream**\n- Called by `aca-launch-outreach`, `aca-campaign-strategy`, or Smartlead-style sequence requests.\n\n**Auto-continue conditions**\n- No mailbox connected: continue to `aca-sender-health`.\n- Copy needs QA: continue to `aca-copy-spam-checker`.\n- Sequence written but deliverability unknown: continue to `aca-email-deliverability-audit`.\n- User also wants LinkedIn: continue to `aca-launch-outreach`.\n\n**Stop before chaining when**\n- Adding contacts or lists the user has not approved.\n- The next step happens in the ACA app (building, enrollment, turning on or pausing).\n\n**Downstream skills**\n- `aca-sender-health`: mailbox readiness.\n- `aca-copy-spam-checker`: QA sequence copy.\n- `aca-email-deliverability-audit`: preflight sequence risk.\n- `aca-launch-outreach`: add a LinkedIn leg.\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, lead_list_id, sequence_id, written sequence, approvals, constraints}\n```\n\n## ACA tools used\n\n- `get_started`, `get_workspace`\n- `list_sequences`, `get_sequence`\n- `list_lead_lists`, `get_lead_list`, `create_lead_list`, `add_contacts_to_list`\n- `bulk_create_contacts`, `get_contact`\n\n## ACA app pages\n\n- Build, enroll, turn on or pause: `https://www.automatedclientacquisition.com/email/sequences`\n- Connect mailboxes: `https://www.automatedclientacquisition.com/email/mailboxes`\n- Deliverability: `https://www.automatedclientacquisition.com/email/analytics`\n"
}