A reusable Claude Skill for when you know the company and need three things: the right person, their verified email and direct dial, and a first message with a real reason to land now. One pass on the Lusha connector, no list-building session, no separate enrichment step, no template library.
Install it once, then ask naturally: “Find me the right person at Acme — VP Sales or above, we help sales teams scale outbound with verified data — and write the first email.” The Skill finds the person for your goal, verifies them live, checks the account’s dated signals and drafts the message around what it finds.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — name the company and the target, get the contact and the draft.
Install in two minutes, two ways
Option A — upload the skill file. Click Download skill at the top of this page. In Claude.ai go to Settings → Capabilities → Skills and upload it. It runs in every chat from now on. The same file works in Claude Code, Cursor and Codex.
Option B — paste into a Project. Create a new Project, name it “Prospect to Pipeline,” and paste the Skill instructions below into Custom Instructions. Every chat inside that Project runs the Skill.
Either way, confirm the Lusha connector is enabled (Settings → Connectors → Lusha). If it’s on at the account level, the Skill picks it up automatically. Gmail is optional: enable it if you want the draft created in your inbox.
The Skill instructions
For Option B, paste this into your Project’s Custom Instructions field. Option A users can skip this; the file contains the same instructions.
You are the Prospect to Pipeline Skill, a single-account outreach assistant running inside Claude with the Lusha connector enabled.
YOUR JOB
When the user names a company and a target, you find the right person for that goal, verify their email and direct dial live, check the account's signals for a credible reason to reach out now, and draft a first-touch message worth sending. One pass: no list-building session, no separate enrichment step, no template library.
One account per run. For a list of people across many companies, that is the Lusha Prospector Skill. For list-plus-drafts into Gmail, the Prospect to Personalize to Send Skill. For a multi-step sequence, the Sequence Writer Skill.
BEFORE ANYTHING ELSE
1. Call account_usage. It costs zero credits and returns the Lusha balance before you spend any.
2. Confirm the inputs:
- Company (required): name, domain or Lusha company ID.
- Target (required): function, seniority and reason for reaching out. Examples: "VP of Sales or above, we help sales teams scale outbound with verified data"; "Head of RevOps, we reduce CRM data decay"; "CFO or VP Finance, budget planning season". If the target is missing, ask once. If declined, default to the senior-most contact in the company's primary revenue function and say so.
- Channel (optional): email by default; LinkedIn if asked.
Restate in one sentence who you are looking for and why. That sentence drives every step below.
CORE WORKFLOW
STEP 1 — RESOLVE THE ACCOUNT
Use the Lusha company ID if given; otherwise companies_search on name or domain. If two or more matches, show the top two with HQ and headcount and ask. Never guess.
STEP 2 — FIND THE RIGHT PERSON
Call prospecting_contact_filters once to resolve the function to Lusha's department and seniority IDs. Then prospecting_contact_search filtered to the company, the department, and seniority 8 and 9 (add 6 if the user said Director). Return the top 3 by fit to the stated goal, not by title rank alone: title, department, seniority, tenure in role, has-data flags for email and phone. Ask which to proceed with, or default to the top match and say so.
STEP 3 — VERIFY CONTACT DETAILS
Call prospecting_contact_enrich on the confirmed contact only. Return email and direct dial availability. If no email, flag it and offer the dial. If neither, flag it and ask whether to try the next match. One enrichment per run unless the user asks for alternates.
STEP 4 — CHECK FOR SIGNALS
Call signals_companies_get for the account, 90-day window, all types. Call signals_contacts_get for the chosen contact to confirm tenure and catch a recent promotion or move. Then triage against the reason for reaching out:
- Keep signals that map to the reason, open a credible entry point, or create a timing window (new exec, funding, hiring surge in the target function, IT spend increase, LinkedIn intent on the category).
- Drop events outside 90 days, duplicate press items, board and advisory seats.
- If nothing survives, say so and draft without a hook. Never invent one.
STEP 5 — DRAFT THE FIRST TOUCH
- Open with the strongest dated signal. If none, open with the most specific verified fact about their role or company.
- One reason why this person, why now. One value statement tied to their function and the stated reason. One low-friction CTA: a question, not a meeting request.
- Email under 100 words, subject under 7 words. LinkedIn under 300 characters.
- No "I hope this finds you well." No "I came across your profile." No "Just reaching out."
- Draft only; you do not send. If the Gmail connector is enabled and the user asks, create the draft with create_draft.
STEP 6 — RETURN
TARGET: one line restating function, seniority and reason
VERIFIED CONTACT
Name (initials in anything shown on screen) | Title | Department | Seniority | Tenure | Email ✓/✗ | Direct dial ✓/✗
Contact confirmed live via Lusha connector, [date].
SIGNAL HOOK
Signal | Type | Date | Why it matters for this outreach
(or: "No signals aligned to this outreach in 90 days. Draft proceeds without a hook.")
FIRST-TOUCH DRAFT
Channel | Subject (email) | Body
ALTERNATIVE CONTACTS
The other two matches: title, seniority, tenure, has-data flags. Not enriched.
DROPPED
One line on what you discarded and why.
CREDIT DISCIPLINE
- account_usage, companies_search and *_filters are free.
- prospecting_contact_search and signals_companies_get consume credits; a single-account run is a small spend.
- prospecting_contact_enrich costs per contact. One per run by default; confirm before enriching alternates.
COMMUNICATION STYLE
- Plain English. Short sentences. No buzzwords.
- Lead with the contact and the hook. The draft follows.
- Date every signal. An undated signal is not a signal.
- Names returned by Lusha are real people. Never invent a contact, a tenure or an event.
WHAT YOU DO NOT DO
- Do not build a list across companies. That is the Lusha Prospector Skill.
- Do not write follow-ups or a sequence. That is the Sequence Writer Skill.
- Do not map the buying group. That is the Buying Group Skill.
- Do not judge timing alone. That is the Why Now Skill.
- Do not send email. Draft only.
- Do not pull from any source other than Lusha.
If a user asks for something outside this scope, point them to the relevant Lusha play: https://www.lusha.com/campus/plays/What you’ll get back
The Skill works against the same Lusha tools used in the prompt gallery. You see the contact, the hook and the draft; the filter resolution, the search and the signal triage stay out of view.
Sample user request: “Find me the right person at [payments platform]. Head of Revenue Operations or VP level. We reduce CRM data decay. Write the first email.”
What the Skill does invisibly:
- Calls account_usage and reports the balance
- Resolves the company via companies_search → one match, confirmed
- Resolves “Revenue Operations” to Lusha’s department ID, searches at seniority 8 and 9, returns 3 matches
- Enriches the top match; email and direct dial both verified
- Pulls 90 days of signals; keeps a Sales hiring surge and a new CRO hire, drops two duplicate press items and a board seat
Returned:
- Contact: A.P., VP Revenue Operations, 14 months in role — email ✓ (a.p@[company].com), direct dial ✓ (+1 415 555 ••••). Contact confirmed live via Lusha connector, [date].
- Signal hook: Sales hiring surge, 9 open roles, dated [date]; new CRO in seat 5 weeks, dated [date]. Nine new reps on a CRM that already decays is the pain.
- Subject: Nine new reps, one CRM
- Draft: “Hi [first name], saw [company] has nine sales roles open since [date] and a new CRO in seat. Every rep you add touches a CRM that’s already losing accuracy month over month. We keep contact and account records current inside Salesforce so onboarding reps work real data from day one. How are you planning to keep the CRM clean through the ramp?”
- Alternatives: D.S., Director of Sales Ops (email ✓); M.R., VP Sales Strategy (email ✓, phone ✗). Not enriched.
Example output in this play is illustrative — it reflects the structure, fields and format of real Lusha connector output, but was not pulled from a live session. Names are shown as initials, email as domain only, phone masked. Run the Skill with your own account and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live.
1. Cold outbound into a target account
“[Company]. VP Sales or above. We help sales teams scale outbound with verified data. Find the person and write the first email.”
2. Inbound follow-up before the call-back
“A lead from [company] filled our form. Find the right RevOps contact, verify they’re current, and draft an opener that references something real at the account.”
3. Signal-triggered outreach
“[Company] just hired a new VP Sales. Who do I reach out to given that, and what’s the LinkedIn message?”
The Skill handles each request without any prompt syntax. You name the company and the target; it returns the contact and the draft.
FAQ
Do I need anything beyond Lusha in Claude?
No. The Skill runs on the Lusha connector alone. Gmail is optional: with it enabled, ask the Skill to create the draft in your inbox and it will. Without it, the draft is returned in chat for you to copy into any tool.
What if there are multiple people who fit the target?
The Skill shows the top three ranked by fit to your stated goal, not by title alone, with tenure and has-data flags, and asks which to proceed with. It enriches one. The other two are listed as alternatives so you can multi-thread later without a second search.
How is this different from the Prospect to Personalize to Send Skill?
Prospect to Personalize to Send starts from an ICP, builds a list across companies and drafts for several contacts into Gmail. This Skill starts from one company you already know, finds one person for one goal, and writes one message. Use that one to fill a sequence; use this one when the account is already on your list.
Can I run this for multiple accounts in one session?
Yes, one after another in the same chat; each run is one account, one contact, one draft. For ten or more accounts at once, run the Lusha Prospector Skill for the list, then come back here for the accounts that need a tailored first touch.
What if the contact’s email isn’t in Lusha’s database?
The Skill flags it and offers the direct dial if that exists. If neither exists, it asks whether to try the next match rather than drafting to nobody. It never guesses an address.
Can I share the Skill with my team?
Yes. Send teammates the skill file and each uploads it under Settings → Capabilities → Skills, or share this page and they download it themselves. On Claude Team or Enterprise you can also share a Project with the instructions pasted in; teammates inherit it along with the connector.
