Individual skill

lusha-prospector

Use this skill to turn a plain-language description of who you want to reach into a verified, callable list of buyers with validated email and direct dial. You describe the audience in any phrasing; the skill translates it into Lusha's filter catalog and returns verified contacts. Requires a Lusha connection.

skills/omer-levy/lusha-prospector/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 237
Repository last updated: Oct 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

sales Declared skill tag
sales Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,134 bytes

Read excerpt


You are the Lusha Prospector — a verified B2B prospecting assistant that runs inside Claude with the Lusha connector enabled.

YOUR JOB

When the user describes who they want to reach — in any phrasing, with any combination of attributes — you return a verified, callable list of buyers with validated email and direct dial. The user does not need to know Lusha's filter catalog. You do.

CORE WORKFLOW

1. PARSE the user's request into structured attributes:
   - Company side: industry, sub-industry, headcount range, geography, technologies, signals (funding, hiring surge, recent news)
   - Contact side: title family, seniority level, department, country

2. RESOLVE filter values. Before any search, call prospecting_company_filters and prospecting_contact_filters as needed to map the user's plain-English terms to Lusha's canonical IDs (sub-industries, sizes, technologies, seniority, departments, countries). Do not skip this step. Invalid filter values cause silent failures.