/prospect-intake

name: prospect-intake
description: Start a new prospect's intake, with or without their files in hand — a request naming a new prospect and attaching no documents is a normal starting point, because Step 1 searches the connected tools or asks the advisor to upload. Cleans and normalizes their account files (statements, exports, screenshots) into a consolidated view, then hands back a plain-English prospect summary, a detailed analyst handoff the full proposal gets built from, and a friendly "what to expect" memo, offered as a Gmail draft on approval. Does not produce the proposal, recommend an allocation, or quote fees. Triggers on "prospect intake", "/prospect-intake", "new prospect intake", "clean up [prospect]'s statements", "process [prospect]'s files", "what to expect note for [prospect]" — and on how an advisor raises a new prospect before any file exists: "I met with a potential client/customer", "[name] is interested in becoming a client", "I have a new prospect", "how should I proceed with [name]".

Prospect Intake

Turn the pile of statements a prospect hands over into something usable — a clean summary they can read, a clean handoff the analyst team can build a full proposal from, and a warm note that keeps the prospect engaged while that happens.

This skill is the **intake step**, not the proposal itself. The full investment proposal (proposed allocation, expected outcomes, fees, transition plan) is built by the firm's analysts from the detailed handoff this skill produces — it is not generated here.

Inputs

Required: the **prospect's name**. Their files are needed too — either found in a connected tool or uploaded — but a request that arrives without them is a normal starting point, not a reason to hold off: **Step 1: Find the Files** below is how they get found, and it is where this skill begins. Never invent holdings.

Step 1: Find the Files

Ask the advisor a single question up front: *do you want me to look for [prospect]'s files in your connected tools, or would you rather upload them here?* Get the prospect's name either way — it's needed for both paths.

**A. Look in connected tools**

Check which systems are actually connected — call `ListConnectors` (load via `ToolSearch` if it isn't already available) — for a CRM (Redtail, Salesforce, Wealthbox), Google Drive, Gmail, and Microsoft 365. Don't guess at a tool-name prefix; for any system whose tools are loaded, use `ToolSearch` with that system's name to find its actual tools.

**Look for the tools before you trust the registry.** `ToolSearch` by the system's own name is the check that decides: if its tools come back, that system is connected and callable — use them. `ListConnectors` can answer "No installed connectors found" even in a session with several live, working connectors, and in some clients it renders a user-facing card rather than returning data at all. So it explains a gap, it never establishes one, and an empty result means **unknown**, never "nothing is connected". When it does return entries, read `enabledInChat`, not `connected`: `connected: true` with `enabledInChat: false` is authenticated but switched off for this chat, so tell the advisor they can enable it here rather than reporting it as unconnected; a missing or `null` `connected` is unknown, not disconnected.

Search all connected systems **in parallel** — one system coming back empty doesn't block reading the others. If this pull is likely to take a moment (several systems connected), say so up front; that's a heads-up, not another "should I start?" gate — the upload-vs-search question above is the only required input before proceeding.

Show the advisor what matched (file names, email subjects, CRM record) before reading any of it — confirm which items are actually the prospect's files before pulling content from them. **Disambiguate first:** if a CRM search turns up more than one matching contact or opportunity, don't pull from or attach to any of them until the advisor confirms which one is correct — same privacy bar as a household match in other skills: never proceed on a name match alone.

If Zocks is also connected, check it for a prior conversation with this prospect and pull whatever facts it already captured (goals, life details, account mentions). Reuse those instead of re-asking the advisor or the prospect for them, and cite them as coming from that conversation rather than treating them as missing in Step 2.

If none of CRM/Drive/Gmail/M365 are connected, say so plainly and fall back to upload.

**B. Upload here**

Wait for the advisor to provide files — PDF/CSV/screenshot, or pasted text. Don't proceed on a promise of files to come; wait for them to actually arrive. Never invent holdings to fill a gap while waiting.

Step 2: Clean the Files

**Dispatch one `claude-for-financial-advisors:statement-extract` subagent per file, all in a single message so the pile is read concurrently** — one `Agent(claude-for-financial-advisors:statement-extract)` call per file, in the same response. Each gets one file path and the prospect's name, and returns that file's accounts as a normalized record with data-quality flags and its inferred-vs-read marking already done. Reading a stack of statements one after another is the slowest part of this skill, and it gets slower the bigger the pile — which is exactly when the advisor is waiting longest.

Consolidation stays with you: the subagents each see one file and cannot tell that an account in file 3 is the same account as one in file 7. Duplicate detection across the set, and the single consolidated view, are yours to assemble from their records.

The extraction schema each subagent works to, which is also what to do by hand if the subagent is unavailable — per account:

• Account type/registration (401(k), IRA, brokerage, etc.) and custodian/provider if shown
• Holdings: ticker/fund name, shares or units, current value, cost basis if present
• Fees visible on the statement
• Sta