match-prospectslisted

# Match Prospects - Reuse Tenant Prospects A skill that surfaces existing prospects already in the LeadAce tenant DB (collected for past projects) that fit the **current** project's targeting, and links the approved ones via `project_prospects` junction rows. This skill never creates new prospects or organizations. To gather brand-new prospects via web search, use `/build-list`. To upload a list from a file, use `/import-prospects`. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline). ## When to use this - The user has run multiple projects and wants to surface overlap (a prospect collected for project A may fit project B). - A new project's target overlaps with an older one and the user wants to skip the discovery cost. - A `do_not_contact` flag set in another project should already protect those prospects automatically — skip the manual exclusion step. ## Inputs - `$0` — project name (required). Must already exist; run `/leadace <your-homepage-URL>` first if not. - `$1` — approximate target count for matched prospects (default 20). The skill stops once that many strong matches are linked. ## Steps ### 1. Resolve the project If `$0` is provided, use it as `PROJECT_NAME`. Otherwise call `mcp__plugin_leadace_api__list_projects`: - exactly one project → use it - multiple → ask via `AskUserQuestion` - none → abort: "N