Update to ACA

{
  "description": "Weekly ACA operating cadence for outbound and content. Use when the user asks for a weekly review, operating rhythm, campaign optimization, experiment planning, Monday/Wednesday/Friday workflow, or \"what should I do this week in ACA\". Reads campaign, reply, list, lead magnet, and content status through the ACA connector and produces a weekly plan.",
  "included_files": [],
  "name": "aca-weekly-rhythm",
  "skill_md_contents": "---\nname: aca-weekly-rhythm\ndescription: Weekly ACA operating cadence for outbound and content. Use when the user asks for a weekly review, operating rhythm, campaign optimization, experiment planning, Monday/Wednesday/Friday workflow, or \"what should I do this week in ACA\". Reads campaign, reply, list, lead magnet, and content status through the ACA connector and produces a weekly plan.\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 weekly rhythm\n\nThis skill turns ACA from a launch tool into an operating system. It reviews the pipeline, picks one or two high-leverage changes, and writes the week's plan.\n\n## Rules\n\n- Use the ACA connector only. Never ask for vendor API keys or run SQL/API calls.\n- Start read-only. Ask before any write.\n- Report counts exactly as returned. `get_campaign_metrics` returns stored counts, never rates. Only state a rate when the matching denominator came back too, and show both numbers.\n- Never invent metrics, replies, or results.\n- Pausing, resuming, or editing campaigns and sequences, running autopilots, and publishing happen in the ACA app. Recommend the change and give the link.\n- Prefer one controlled experiment at a time.\n- Keep the output operational: what changed, what to do next, and what is blocked.\n- If a tool result includes `plan_note` or `plan.limitation`, relay it as a plain fact. Never promote plans, pricing, or upgrades.\n\n## Workflow\n\n### 1. Run the brief\n\nCall `get_started` first (fallback: `get_workspace`). Then read in parallel:\n\n- `list_campaigns`, then `get_campaign_metrics` for each active campaign\n- `search_conversations` with `has_inbound_message: true` for replies\n- `list_sequences`\n- `list_lead_lists`\n- `list_lead_magnets`\n- `list_content_ideas` and `list_content_generation_jobs`\n\nMailbox and sender health are not available through the connector. Use the mailbox and LinkedIn counts from `get_started` and point to `/email/mailboxes` and `/email/analytics` for health.\n\n### 2. Diagnose by cadence\n\n**Monday: plan and refill**\n\n- Lead lists behind active campaigns that are small or exhausted\n- Content queue light (few unused ideas, no recent generation jobs)\n- Choose campaign, list, and content priorities for the week\n- Route to `aca-find-leads` or `aca-content-week` when needed\n\n**Wednesday: experiment and unblock**\n\n- Active campaigns with little progression in their stored counts\n- Replies waiting more than a day\n- Pick one experiment: audience, hook, channel, offer, or timing\n- Draft the change in chat; the user applies it at `/campaigns/{id}` or `/email/sequences`\n\n**Friday: review and clean**\n\n- Summarize wins, replies, failed generation jobs, and list quality problems\n- Identify contacts to tag, re-stage, or suppress (route to `aca-positive-reply-scoring` for replies)\n- Write the weekly note\n\n### 3. Write the weekly note\n\nWrite it in chat with:\n\n- Week and date\n- Metrics snapshot (stored counts as returned)\n- Decisions\n- Experiment hypothesis\n- Next actions with owner and link\n\nOffer to let the user save it at `/assets?tab=strategies`.\n\n### 4. Optional actions\n\nOnly after approval, through the owning skill:\n\n- Refill a lead list: `aca-find-leads`\n- Draft a new campaign: `aca-launch-outreach`\n- Add ideas or generate content: `aca-content-week`\n- Tag or re-stage replying contacts: `aca-positive-reply-scoring`\n\nApp-only, give the link:\n\n- Pause or resume a campaign: `/campaigns/{id}`\n- Turn a sequence on or off: `/email/sequences`\n- Run or pause an autopilot: `/autopilots`\n\n## Output format\n\n```text\nACA Weekly Rhythm - {week}\nWorkspace: {workspace} ({stage})\n\nStatus:\n- Campaigns: {summary with stored counts}\n- Replies: {N with inbound messages, N waiting on you}\n- Leads: {summary}\n- Content: {ideas, jobs}\n- Senders: {N LinkedIn, N mailboxes}; health at /email/analytics\n\nThis week's priority:\n{one priority}\n\nExperiment:\nHypothesis: {hypothesis}\nChange: {change}\nMetric: {metric, as a stored count with its denominator}\n\nActions:\n1. {action} → {skill or app link}\n2. {action} → {skill or app link}\n```\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 by the user on a weekly cadence or after `aca-pipeline-status`.\n\n**Auto-continue conditions**\n- Lead lists running low: continue to `aca-find-leads`.\n- Content queue low: continue to `aca-content-week`.\n- Replies need review: continue to `aca-positive-reply-scoring`.\n- A test is needed: continue to `aca-experiment-design`.\n- Campaign or sender issue: continue to `aca-deliverability-incident-response`.\n\n**Stop before chaining when**\n- The next step changes live campaigns, publishes, or imports. Those happen in the app.\n- Creating records the user has not approved.\n\n**Downstream skills**\n- `aca-find-leads`: refill the audience.\n- `aca-content-week`: refill content.\n- `aca-positive-reply-scoring`: learn from replies.\n- `aca-experiment-design`: plan the next test.\n- `aca-deliverability-incident-response`: handle blockers.\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, job_id, approvals, constraints}\n```\n\n## ACA tools used\n\n- `get_started`, `get_workspace`\n- `list_campaigns`, `get_campaign_metrics`\n- `search_conversations`\n- `list_sequences`\n- `list_lead_lists`\n- `list_lead_magnets`\n- `list_content_ideas`, `list_content_generation_jobs`\n\n## ACA app pages\n\n- Campaigns: `https://www.automatedclientacquisition.com/campaigns/{id}`\n- Sequences: `https://www.automatedclientacquisition.com/email/sequences`\n- Mailbox health: `https://www.automatedclientacquisition.com/email/mailboxes`, `/email/analytics`\n- Autopilots and publishing: `https://www.automatedclientacquisition.com/autopilots`, `/publish-queue`\n- Save the weekly note: `https://www.automatedclientacquisition.com/assets?tab=strategies`\n"
}