Stats
Actions
Tags
From lusha
Find companies or contacts triggered by a buying signal, then surface verified phone numbers for the right decision makers. Use when the user says "find companies that just raised funding", "who's surging in sales hiring right now", "show me companies with headcount growth", "find contacts who just got promoted", "who changed jobs recently in [industry]", "show me [title] at companies that just [signal event]", or any request that starts with a real-world trigger rather than a static filter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lusha:signal-prospectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Start from a buying signal — company or contact level — and end with a call-ready list of enriched decision makers. This is Lusha's core differentiated workflow: trigger → identify → phone reveal.
Start from a buying signal — company or contact level — and end with a call-ready list of enriched decision makers. This is Lusha's core differentiated workflow: trigger → identify → phone reveal.
Determine which mode applies based on the user's request:
Company signal mode — the trigger is something happening at a company (funding, hiring surge, headcount change, news event). Goal: find the right people at those companies and get their phones.
Contact signal mode — the trigger is something happening to a person (got promoted, changed company). Goal: find those people and get their updated contact details.
If unclear, ask: "Are you looking for companies showing a specific signal, or individual contacts who recently changed roles or employers?"
These tools are the authoritative source of valid signal identifiers — never assume a signal type exists without confirming it here, since invalid values are rejected with a 400.
Company signals: Call signals_company_filters with no filterType to get the directory: { signalTypes, availableFilters: [{ filterType, requiresQuery }] }. To enumerate the values for a sub-filter, call it again with filterType set to newsEventTypes, hiringByDepartments, or hiringByLocations (hiringByLocations requires a query).
Contact signals: Call signals_contact_filters to get the supported contact signal types (e.g. promotion, companyChange, allSignals).
Match the user's phrasing to a signal identifier returned in Step 2. The table is a starting point — always validate the identifier against the live directory before using it:
| User says | Signal type (names) | News sub-type (applied in Step 5) |
|---|---|---|
| "raised funding / Series A/B/C / IPO" | financialEventsNews | Funding Round, IPO, Strategic Investment |
| "surging in hiring / lots of open roles" | surgeInHiring | — |
| "growing fast / headcount up" | headcountIncrease3m / headcountIncrease6m | — |
| "hiring sales reps" | surgeInHiringByDepartment (+ filterByDepartment) | — |
| "new partnership / new customer" | commercialActivityNews | New Customer, Partnership, New Location |
| "new product launch" | productActivityNews | Product Launch, Product Integration |
| "executive just joined / new CRO" | peopleNews | Executive Hire, Executive Departure |
| "contact just got promoted" | contact signal promotion | — |
| "contact changed company / new job" | contact signal companyChange | — |
The signal type (names) is what the discovery search in Step 4 accepts. The news sub-type (right column) is a different mechanism — it cannot be passed to the discovery search; it is applied in Step 5 via signals_company_filters values. If the user's intent doesn't map cleanly, present the closest available types and confirm.
Discovery narrows the population to companies/contacts that currently have the signal. The signals filter on the prospecting search tools is what does this — it accepts signal type names plus hiring sub-filters only.
Company signal mode — prospecting_company_search with:
signals: {
names: ["<signal type>", ...], // OR-combined; from Step 2/3
startDate: "YYYY-MM-DD", // optional; defaults to last 6 months
filterByDepartment: [{ department }], // optional; for surgeInHiringByDepartment
filterByLocation: [{ country, state }]// optional; for surgeInHiringByLocation
}
Combine with ordinary company filters (industry, size, location — resolved via prospecting_company_filters) to scope the account population. News-event types like Funding Round cannot be narrowed here — pass the parent type (financialEventsNews) and narrow in Step 5.
Contact signal mode — prospecting_contact_search with signals: { names: [...], startDate? } (contact signals support names + startDate only). Request up to 50 results (page_size).
The discovery search returns the matched companies/contacts but not the underlying signal events or their dates. To surface the actual event, its date, and to keep only a specific news sub-type, run a signals lookup on the matched Lusha IDs:
Company mode — signals_companies_get with the matched company IDs. Pass filters.include.newsEventTypes (e.g. ["Funding Round"]), hiringByDepartments, or hiringByLocations to keep only the events you care about. Returns the signal events, date window, and billing.creditsCharged.
Contact mode — signals_contacts_get with the matched contact IDs → promotion / company-change events with dates.
This step consumes credits per signal returned, so run it only on the shortlist you intend to act on, and state the cost first. If you have company/contact identifiers but no Lusha IDs (e.g. a user-supplied list of domains), use signals_companies_search / signals_contacts_search instead — they resolve the identifier and return signals in one call.
For the matched companies, use prospecting_contact_search scoped to them via companyDomains or companyNames, plus the target role — jobTitles (free-form) or resolved seniority / departments. If no role was specified, ask: "What role are you looking to reach at these companies?"
Skip this step in contact signal mode — the triggered contacts are already the targets.
Use prospecting_contact_enrich with the contact ids to reveal direct and mobile numbers. Set reveal from each result's canReveal[].field; up to 50 contacts per call. Sum the canReveal[].credits and state the total before enriching large batches — use account_usage to confirm the balance if needed.
State exactly which signal was applied and what it means (e.g., "Funding Round events since 2026-05-01").
Company signal mode:
| # | Company | Signal | Signal Date | Contact Name | Title | Direct Phone | Mobile |
|---|
Contact signal mode:
| # | Name | Signal | Previous Role | New Role / Company | Direct Phone | Mobile |
|---|
—headcountIncrease3m alongside funding)Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub lusha-oss/lusha-mcp-plugin --plugin lusha