ClaudeSuperPower
SubmitLog in

signal-prospect

Skill

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

0Marketing

Install

git clone https://github.com/lusha-oss/lusha-mcp-plugin.git ~/.claude/skills/signal-prospect

What is signal-prospect?

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.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~124 tokens of context used while enabled, before you invoke anything

Documentation

README · ~5 min read

Signal-Prospect

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.

Step 1 — Identify the Signal Mode

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?"

Step 2 — Discover Available Signal Types and Sub-Filters

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).

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.