Update to ACA

{
  "description": "Plan and build a target list of leads in ACA. Use when the user says \"find leads\", \"build a list of [role] in [industry]\", \"import [N] [persona]\", \"search LinkedIn for [criteria]\", \"populate the audience for [campaign]\", or asks to source prospects. Turns a vague audience into precise search criteria, sends the user to the right ACA sourcing page, then picks up and verifies the resulting list.",
  "included_files": [],
  "name": "aca-find-leads",
  "skill_md_contents": "---\nname: aca-find-leads\ndescription: Plan and build a target list of leads in ACA. Use when the user says \"find leads\", \"build a list of [role] in [industry]\", \"import [N] [persona]\", \"search LinkedIn for [criteria]\", \"populate the audience for [campaign]\", or asks to source prospects. Turns a vague audience into precise search criteria, sends the user to the right ACA sourcing page, then picks up and verifies the resulting list.\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# Find leads in ACA\n\nACA stores prospects as contacts grouped into lead lists. This skill turns a brief into a campaign-ready lead list. The search itself runs in the ACA app; this skill does the targeting work, then checks what landed.\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 LinkedIn, Apify, Prospeo, or other provider API keys; ACA owns those integrations.\n- Never invent people, emails, companies, or counts. Prospects come from ACA searches the user runs, or from data the user pastes.\n- The connector cannot search ACA's lead database or run LinkedIn imports. Define the criteria in chat, then send the user to `/list-building` (database search) or `/leads/import` (LinkedIn search URL or CSV).\n- Ask before any write: creating a list, adding contacts, or adding pasted people.\n- If a brief is too broad, narrow by industry or SIC category, keyword, geography, company size, seniority, email status, or LinkedIn presence.\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. Read the workspace\n\nCall `get_started` to see counts (contacts, lead lists, ICPs) and next steps. If it is not available, call `get_workspace` and `list_lead_lists`.\n\nCheck whether a suitable list already exists with `list_lead_lists`, and whether matching contacts are already in ACA with `search_contacts`. Reuse before sourcing.\n\n### 2. Clarify the audience\n\nIf the brief is vague, ask one short question. Extract:\n\n- Buyer role and seniority\n- Industry or SIC category\n- Geography\n- Company size\n- Desired count\n- Required channels (email, LinkedIn, phone)\n- Disqualifiers\n\nIf the user references a saved ICP, ask them to paste its key traits; `get_started` only tells you whether ICPs exist.\n\n### 3. Write the search spec\n\nProduce a precise spec the user can enter in ACA:\n\n```text\nSearch spec: {list name, e.g. \"US HVAC Owners - May 2026\"}\nWhere: /list-building (database) | /leads/import (LinkedIn)\nRoles / seniority: {titles, seniority levels}\nIndustry: {SIC codes or keywords}\nGeography: {country / state / city}\nCompany size: {min-max employees}\nChannel requirements: {has email, email status, has LinkedIn, has phone}\nExclude: {titles, industries, keywords}\nTarget count: {n}\n```\n\nPick the source:\n\n- **Database search at `/list-building`** first. It is the fastest route for most B2B and local briefs.\n- **LinkedIn import at `/leads/import`** when the database is thin, the user wants LinkedIn-first outreach, or the brief depends on LinkedIn-only filters. Describe the LinkedIn or Sales Navigator search to build (keywords, title, geography, industry, company headcount), and remind the user to check for an already running import before starting another.\n- **CSV at `/leads/import`** when the user has a file.\n\nIf the user pastes people directly in chat (names, companies, emails, LinkedIn URLs), confirm the count and fields, then add them with `bulk_create_contacts` (100 per call) after approval. Never fill in missing fields yourself.\n\n### 4. Pick up the results\n\nWhen the user says the build or import is done, call `list_lead_lists` to find the new list, then `get_lead_list` to confirm size and sample rows. If contacts were imported without a list, find them with `search_contacts`, then offer to `create_lead_list` and `add_contacts_to_list`.\n\nCompare the sample against the spec. If titles, geography, or size drift, tighten the spec and send the user back to the same page.\n\n### 5. Hand off\n\nIf the list needs grading or cleanup, route to `aca-lead-quality`. If it is already clean, route to `aca-launch-outreach`.\n\n## Output format\n\n```text\nLead list: {list_name}\nList ID: {list_id}\nSource: {ACA database search / LinkedIn import / CSV / pasted}\nContacts: {count from get_lead_list}\nSample:\n- {name} - {title}, {company}\n\nSpec fit: {matches / drift on ...}\nNext: {aca-lead-quality or aca-launch-outreach}\n```\n\nBefore the list exists, output the search spec and the page link instead, and stop.\n\n## Skill chaining\n\nPreserve the workspace, relevant IDs, the search spec, 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 automatically; otherwise end with the handoff block.\n\n**Upstream**\n- Called by `aca-kickoff`, `aca-campaign-strategy`, `aca-auto-research`, or any sourcing-specific skill.\n\n**Auto-continue conditions**\n- Local vertical or geography brief: continue to `aca-local-business-leads` if not already there.\n- Seed customer or lookalike brief: continue to `aca-lookalike-leads` if not already there.\n- Domain or account list brief: continue to `aca-domain-list-builder` if not already there.\n- Competitor or category brief: continue to `aca-competitor-engagers` if not already there.\n- List exists in ACA: continue to `aca-lead-quality`.\n\n**Stop before chaining when**\n- The search or import still has to run in the ACA app.\n- Creating lists or adding contacts the user has not approved.\n\n**Downstream skills**\n- `aca-local-business-leads` - geo and vertical local list.\n- `aca-lookalike-leads` - lookalike audience.\n- `aca-domain-list-builder` - account or domain based list.\n- `aca-competitor-engagers` - competitor or category audience.\n- `aca-lead-quality` - grade and segment the resulting list.\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, search spec, lead_list_id, approvals, constraints}\n```\n\n## ACA tools used\n\n- `get_started`, `get_workspace`\n- `search_contacts`, `bulk_create_contacts`\n- `list_lead_lists`, `get_lead_list`, `create_lead_list`, `add_contacts_to_list`\n\n## ACA app pages\n\n- Database search: `https://www.automatedclientacquisition.com/list-building`\n- LinkedIn or CSV import: `https://www.automatedclientacquisition.com/leads/import`\n- Lead lists: `https://www.automatedclientacquisition.com/leads/lists`\n"
}