--- name: find-person description: Use this skill whenever the user wants to find or look up a person by name and company — but does NOT already have a LinkedIn URL for them. --- # Find Person Use `MoltSets:linkedin_slug_search` to locate a person by name and company domain. ## Triggers Triggers include phrases like "find me [Name]", "look up [Name] at [Company]", "can you find [Name]", "search for someone named [Name]", or any request to locate a specific person without a LinkedIn URL already provided. Do NOT use this skill if the user already has a LinkedIn URL� use the enrich-contact skill instead. ## What the tool accepts - `name` — full name (parsed into first/last automatically), e.g. `"Jane Smith"`. OR use `first_name` + `last_name` separately. - `company` or `company_domain` — must be a **domain** (e.g. `acme.com`), not a company name. URLs are normalised automatically. - `count_only` — boolean. Free, no credits charged. Returns only the result count. **There is no job title parameter.** If the user only provides a title and no name, tell them a name is required. ## Set Expectations Before firing any calls, give the user a brief, dry heads-up on what's about to happen. Deadpan over enthusiastic — no filler, no corporate speak. Facts to convey: - 1 free count check, then a full search if there's a match - A few seconds total - If count_only returns 0: you'll retry with looser parameters before giving up ## Step 1 — Resolve the company domain If the user gives a company name (e.g. "HubSpot") rather than a domain: - Infer the domain confidently for well-known companies (HubSpot → `hubspot.com`, Salesforce → `salesforce.com`, etc.) - For unfamiliar companies, ask the user: "What's their website domain?" before proceeding ## Step 2 — Run count_only first (free) Always call the tool with `count_only: true` before committing to a full search: - **0 results** → loosen parameters. Try without the company domain, or check the name spelling. Tell the user what you tried. - **1 result** → proceed to full search immediately - **2+ results** → tighten if possible (add domain if missing), then run the full search and present all results for confirmation ## Step 3 — Full search and present results **One result:** - Show: Name | Title | Company | LinkedIn URL - Ask: "Is this the right person? I can pull their contact info if so." **Multiple results:** - Present as a numbered list: Name | Title | Company | LinkedIn URL - Ask the user to pick one before enriching **No results after loosening:** - Tell the user clearly and ask for more detail (full name, domain) ## After confirmation Once the user confirms the right profile, hand off to the **enrich-contact** skill to retrieve email and/or phone. ## Edge cases - Never pass a company name as the `company` parameter — only domains are accepted - If the user provides a LinkedIn URL directly, skip this skill and go to enrich-contact - Do not invent or guess LinkedIn URLs — only surface what the tool returns - If only a first name is provided with no domain, run count_only first; if the count is high, ask for a last name or domain before spending a credit PKKm�\:��   ��SKILL.mdPK6;