lookalike-prospect
Find companies or contacts similar to a set of references, then enrich results with verified phone numbers. Use when the user says "find companies like my best customers", "find more contacts like these", "expand from these accounts", "who else looks like [company]", "find similar companies to [list]", or any request to discover lookalike targets from a reference set. Requires at least 5 reference companies or contacts for quality results.
What this skill does
# Lookalike Prospect Expand an ICP from a reference set of known-good companies or contacts. Requires a minimum of 5 references — the lookalike model degrades significantly below this threshold. ## Step 1 — Validate Input Count Count the number of reference companies or contacts provided. **If fewer than 5 are provided**, stop and explain before doing anything else: > "Lusha's lookalike model needs at least 5 reference [companies/contacts] to return quality results — fewer than that produces unreliable matches. You've provided [N]. Can you add [5−N] more?" Do not proceed until the user has provided at least 5 references. **If 5 or more are provided**, confirm the reference set with the user: > "Running lookalike search using these [N] [companies/contacts] as the reference set: [list]. Shall I proceed?" ## Step 2 — Determine Mode Based on the user's input, determine whether this is a **company lookalike** or **contact lookalike** search: - References are company names or domains → **company mode** - References are person names, emails, or titles → **contact mode** - Mixed input → ask the user to clarify ## Step 3 — Resolve Reference IDs **Company mode:** Use `mcp__lusha__companies_search` to resolve each reference company to a Lusha company ID. If a company can't be resolved, flag it and ask the user to confirm a substitute or proceed without it (only if at least 5 remain). **Contact mode:** Use `mcp__lusha__contacts_search` to resolve each reference person to a Lusha contact ID. Apply the same fallback logic if a contact can't be resolved. ## Step 4 — Run Lookalike Search **Company mode:** Use `mcp__lusha__lookalike_companies` with the resolved company IDs. Request up to 25 results. **Contact mode:** Use `mcp__lusha__lookalike_contacts` with the resolved contact IDs. Request up to 25 results. ## Step 5 — Find Decision Makers (Company Mode Only) For each lookalike company, use `mcp__lusha__prospecting_contact_search` to find the right contacts. If the user hasn't specified a target role, ask: *"What title or seniority are you targeting at these companies?"* Resolve title/seniority filters via `mcp__lusha__prospecting_contact_filters` before searching. ## Step 6 — Enrich and Reveal Phones Use `mcp__lusha__prospecting_contact_enrich` on the top results to reveal direct and mobile numbers. State the credit count before enriching batches larger than 10. ## Step 7 — Present Results ### Reference Set Used List the [N] references that were used. Flag any that could not be resolved. ### Lookalike Results **Company mode:** | # | Company | Industry | Size | Revenue | Location | Contact Name | Title | Direct Phone | Mobile | Email | |---|---------|----------|------|---------|----------|-------------|-------|-------------|--------|-------| **Contact mode:** | # | Name | Title | Company | Industry | Direct Phone | Mobile | Email | |---|------|-------|---------|----------|-------------|--------|-------| - Phone columns always appear before email — never reversed - Mark missing phones with `—` ### Summary - Lookalike [companies/contacts] found: X - Decision makers enriched: Y - Verified phones revealed: Z ## Step 8 — Offer Next Actions 1. **Narrow results** — apply additional filters (industry, geography, company size) to the lookalike list 2. **Cross with signals** — run `signal-prospect` on this lookalike list to surface which ones are showing buying signals right now 3. **Expand the reference set** — add more references to improve match quality 4. **Export** — format as CSV
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.