Update to ACA

{
  "description": "Get a read-only status report on everything running in ACA right now: active campaigns, replies waiting, email sequences, lead lists, lead magnets, and content generation jobs. Use when the user says \"what's running\", \"status report\", \"morning brief\", \"what's happening in ACA\", \"give me a summary\", or \"anything need attention\".",
  "included_files": [],
  "name": "aca-pipeline-status",
  "skill_md_contents": "---\nname: aca-pipeline-status\ndescription: \"Get a read-only status report on everything running in ACA right now: active campaigns, replies waiting, email sequences, lead lists, lead magnets, and content generation jobs. Use when the user says \\\"what's running\\\", \\\"status report\\\", \\\"morning brief\\\", \\\"what's happening in ACA\\\", \\\"give me a summary\\\", or \\\"anything need attention\\\".\"\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 pipeline status report\n\nA read-only operating brief across the connected ACA workspace. It should be short, specific, and built only from what the connector returns.\n\n## Rules\n\n- Use the ACA connector only. Never ask for vendor API keys or run SQL/API calls.\n- Read-only. This skill creates and changes nothing.\n- Report counts exactly as returned. `get_campaign_metrics` returns stored counts, never rates. Only show a rate when both the numerator and its matching denominator came back in the same result, and label it with both numbers (for example \"12 replies of 140 messaged\").\n- Never invent data. If a tool call fails, report the partial result and name the failed call.\n- Omit empty sections unless the workspace is completely empty.\n- Surface genuine blockers plainly: active campaigns with no leads or no progression, lead lists with zero members behind a live campaign, failed generation jobs, replies nobody has answered, zero connected senders or mailboxes.\n- Mailbox and sender health (bounces, warmup, disconnects, deliverability) is not available through the connector. Report the counts from `get_started` and link to the app pages.\n- The connection is bound to one workspace. To report on another workspace (for example an agency client), the user switches their active workspace in ACA and reconnects, then runs this skill again.\n\n## Workflow\n\n### 1. Read the workspace\n\nCall `get_started`. Note `workspace`, `stage`, `counts` (contacts, lead lists, campaigns, active campaigns, connected LinkedIn accounts, mailboxes), `plan`, and `next_steps`.\n\nIf `get_started` is not available, call `get_workspace` and rely on the list calls below.\n\nIf the stage is `new` or every count is zero, say \"Nothing running yet\" and route to `aca-kickoff`.\n\n### 2. Run independent reads\n\nRun these in parallel:\n\n1. `list_campaigns` (all statuses, so active and paused both show)\n2. `search_conversations` with `has_inbound_message: true` for recent replies\n3. `list_sequences`\n4. `list_lead_lists`\n5. `list_lead_magnets`\n6. `list_content_generation_jobs`\n\n### 3. Drill in only where needed\n\n- For each active campaign that looks stalled or is the user's focus, call `get_campaign_metrics` (and `get_campaign` if you need the sequence summary or lead list).\n- For replies, call `get_conversation` only on the few that look unanswered or high-intent, to say who replied and what they asked. Do not summarize every thread.\n- For a lead list behind an active campaign that looks empty, the count from `list_lead_lists` is enough; do not page through members.\n\n## Output structure\n\n```text\nACA Status - {timestamp}\nWorkspace: {workspace} ({stage})\n\nCAMPAIGNS\n- {N} active, {N} paused, {N} draft.\n- Needs attention: {campaign} - {reason, with the stored counts that show it}\n\nREPLIES\n- Conversations with an inbound message: {N} (from this page of results)\n- Waiting on you: {contact} - {one-line ask}\n\nEMAIL\n- Mailboxes connected: {N} (from get_started)\n- Sequences: {N} total, {N} active\n- Health: not available here; check /email/mailboxes and /email/analytics\n\nLEADS\n- Lead lists: {N}; behind active campaigns: {list} ({members})\n\nLEAD MAGNETS\n- {N} active; captures {N}, delivered {N} (as returned)\n\nCONTENT\n- Generation jobs: {N} in progress, {N} completed, {N} failed\n\nNothing else needs attention.\n```\n\n## Edge cases\n\n- Empty workspace: say \"Nothing running yet\" and route to `aca-kickoff`.\n- User asks for a date range: the connector reports current state and recent items. Say which sections are current-state only rather than estimating a period.\n- Agency user asks for all clients: explain the connection covers one workspace. They switch the active workspace in ACA, reconnect, and rerun the report per client.\n- User asks to pause, resume, or fix a campaign: that happens at `/campaigns/{id}`. Give the link.\n\n## Skill chaining\n\nPreserve the workspace, relevant IDs, the user's brief, and approval state when continuing into another ACA skill. If the user asked for execution and a downstream condition is met, continue into the next skill; otherwise end with the handoff block.\n\n**Upstream**\n- Called after launches, during daily checks, or by `aca-weekly-rhythm`.\n\n**Auto-continue conditions**\n- Workspace empty: continue to `aca-kickoff`.\n- Main bottleneck unclear: continue to `aca-auto-research`.\n- Deliverability or sender blocker: continue to `aca-deliverability-incident-response` or `aca-sender-health`.\n- Replies need review: continue to `aca-positive-reply-scoring`.\n\n**Stop before chaining when**\n- The downstream skill would write anything; this skill stays read-only.\n\n**Downstream skills**\n- `aca-kickoff`: start an empty workspace.\n- `aca-auto-research`: choose the next best action.\n- `aca-deliverability-incident-response`: triage campaign or send problems.\n- `aca-positive-reply-scoring`: review replies.\n- `aca-weekly-rhythm`: turn status into an operating plan.\n\n**Handoff block**\n\n```text\nChain state: {continue|needs_approval|blocked|complete}\nNext skill: {aca-skill-name|none}\nReason: {why this handoff is or is not needed}\nCarry forward: {workspace, stage, campaign_id, lead_list_id, sequence_id, conversation_ids, job_id, constraints}\n```\n\n## ACA tools used\n\n- `get_started`, `get_workspace`\n- `list_campaigns`, `get_campaign`, `get_campaign_metrics`\n- `search_conversations`, `get_conversation`\n- `list_sequences`\n- `list_lead_lists`\n- `list_lead_magnets`\n- `list_content_generation_jobs`\n\n## ACA app pages\n\n- Campaigns (pause, resume, edit): `https://www.automatedclientacquisition.com/campaigns/{id}`\n- Inbox: `https://www.automatedclientacquisition.com/inbox`\n- Mailbox health: `https://www.automatedclientacquisition.com/email/mailboxes`, `/email/analytics`\n- Senders: `https://www.automatedclientacquisition.com/accounts`\n- Autopilots and publishing: `https://www.automatedclientacquisition.com/autopilots`, `/publish-queue`\n"
}