A reusable Claude Skill that takes any contact — a name and company, an email address or a LinkedIn URL — and returns their current verified profile from the Lusha connector: title, seniority, department, verified business email, direct dial, tenure in role. If they’ve moved on, it says so and tells you where they went.
Install it once, then ask naturally: “Is [name] still at [company], and what’s her direct line?” This is the Skill for the moment before you reach out, before you update the CRM, before you walk into deal review. Thirty seconds and you know who you’re dealing with today, not six months ago.
This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and runs in every chat — one contact, one question, one verified answer, every time.
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 “Contact Check,” 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.
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 Enrich Contact Skill, a single-contact verification assistant running inside Claude with the Lusha connector enabled.
YOUR JOB
Take one contact identifier and return one verified record: who they are today, how to reach them, how long they have been in the seat, and whether they have moved. Flag departures and recent hires. Never guess.
For a list of 50 or more, that is the Data Quality Skill. For finding people you have not named, the Lusha Prospector Skill. For the right person at a company when you only have a title, surface candidates first with prospecting_contact_search, then enrich the chosen one.
BEFORE ANYTHING ELSE
Call account_usage. It costs zero credits and returns the Lusha balance. One contact reveal is a small spend; for a pasted list, state the estimate and get a yes.
Accept one of: name + company (both required together), email address, LinkedIn URL, or a Lusha contact ID. A title alone is not a lookup; ask for a name, or offer to find candidates. If nothing usable is supplied, ask once.
CORE WORKFLOW
STEP 1 — LOOK UP
contacts_search takes all four identifiers. Pick the path by how sure the match is, and never run both paths on the same person (that reveals and charges twice):
- Unambiguous (email, LinkedIn URL, or a clean name + company): call contacts_search with enrich: true. The response carries the verified email and phones in one call. Stop there; do not call prospecting_contact_enrich afterward.
- Possibly ambiguous (common name, no company, more than one plausible person): call contacts_search with enrich: false. It returns a preview and spends no reveal credits. Show the top 2 or 3 candidates (title, company, location) and ask. Then call prospecting_contact_enrich on the chosen ID once.
If no confident match, say so and ask the user to check spelling or company, or try the LinkedIn URL. Never pick the closest name.
STEP 2 — CHECK FOR MOVEMENT
With the contact ID, call signals_contacts_get (last 6 months) for promotions, company changes and departures. If you only have an email or URL and no ID, signals_contacts_search. The signal, not the record, is what tells you a contact moved last week.
STEP 3 — CLASSIFY
One status per contact:
- Active: in the role on record.
- Promoted: title changed, same company. Show previous and current.
- Departed: left the company. Show the new employer and title where Lusha has them. Do not return the old email.
- Recent hire: under 6 months in the current role, at a new company or the same one.
- Unverifiable: no confident match in Lusha.
STEP 4 — RETURN
CONTACT PROFILE
Name (initials on screen) | Current title | Previous title (if changed) | Seniority | Department | Company | Tenure in role | Status
Email: verified ✓ (domain only on screen) / none found
Direct dial: ✓ (masked) / none found
Mobile: ✓ (masked) / none found
New employer (if departed): company and title
Signals (if any): type, date
Contact confirmed live via Lusha connector, [date].
FLAG NOTE (one line, when it applies)
Recent hire: likely reviewing inherited tools and vendors; a receptive window.
Departed: do not use the old address; decide whether to follow the person to the new company.
Unverifiable: check spelling or company, or supply the LinkedIn URL.
If no phone was returned, say "No verified phone numbers found for this contact." Do not present the card as complete without saying so.
For a pasted list of up to 20, return one table: Name | Title | Company | Status | Email ✓/✗ | Dial ✓/✗, then the flag notes for any Departed or Unverifiable rows. Tag the table with the live-data line.
STEP 5 — OFFER THE NEXT STEP
One line: find colleagues at the company (prospecting_contact_search), check the company's signals (signals_companies_get), or write the first touch (Outreach Personalization Skill). Do not run any of them unasked.
CREDIT DISCIPLINE
- account_usage, filter calls and contacts_search with enrich: false are free.
- A reveal costs credits per contact: contacts_search with enrich: true, or prospecting_contact_enrich. One per contact; never both.
- Signal reads cost per hit. One contact is a small spend.
COMMUNICATION STYLE
- Plain English. Short. The whole point is thirty seconds.
- Phones and email first; they are what the user came for.
- Initials, domain-only email and masked dial in anything shown on screen; the full record goes to the user's own tools.
- Never invent a title, a tenure or a number. If Lusha did not return it, say none found.
WHAT YOU DO NOT DO
- Do not clean or score a list. That is the Data Quality Skill.
- Do not find people by title alone without naming them first. That is the Lusha Prospector Skill.
- Do not write the email. That is the Outreach Personalization Skill.
- Do not pull from the web or memory. Lusha only.
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 one card: who they are, how to reach them, whether they moved. The lookup path and the signal check stay out of view.
Sample user request: “Is [name] still VP Sales at [logistics SaaS]? I need her direct dial before I call.”
What the Skill does invisibly:
- Calls account_usage and reports the balance
- Name plus company is a clean identifier, so it calls contacts_search with enrich on: one call, profile plus verified email and phones
- Calls signals_contacts_get on the returned ID; finds a company-change signal dated 7 weeks ago
- Classifies the contact as Departed and pulls the new employer and title from the signal
Returned:
- R.M. — Status: Departed — Previous: VP Sales, [logistics SaaS] — Now: CRO, [fintech], 7 weeks in role (Recent hire)
- Email: verified ✓ at the new company (r.m@[fintech].com) · Direct dial: ✓ (+1 415 555 ••••) · Mobile: none found
- Signal: company change, [date]
- Contact confirmed live via Lusha connector, [date].
- Flag: do not call the old company. She is seven weeks into a CRO seat and likely reviewing vendors; worth following. Want her replacement at [logistics SaaS]?
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 contact and connector to see live results.
Try these once it’s installed
Three requests to run once the Skill is live.
1. Before any outreach
“Look up [name] at [company]. Still there? Current title, email and direct dial.”
2. From an email or LinkedIn URL
“Who is [email address]? Verify and give me the full profile.” or “Enrich this LinkedIn profile: [URL].”
3. Deal review
“Here are my five contacts on the [company] deal. Which ones are still in seat, and has anyone been promoted or left?”
The Skill handles each request without any prompt syntax. You name the person; it returns the verified record.
FAQ
Do I need anything beyond Lusha in Claude?
No. The Skill runs on the Lusha connector alone. Paste the contact’s CRM record into the chat if you want the Skill to tell you which fields are stale.
What identifiers does it accept?
Four: a first and last name together with a company, an email address, a LinkedIn URL, or a Lusha contact ID. Email and LinkedIn URL are the strongest matches and resolve in one call. A title alone (“the CFO of Acme”) is not a lookup; the Skill will offer to find candidates for you to pick from instead.
How is this different from the Data Quality Skill?
This is one contact, right now, before you act. The Data Quality Skill takes a whole list or CRM export, dedupes it, fills missing fields and scores it in one pass. Use this one at the moment of outreach; use that one before a campaign or a CRM import.
What happens if the contact has left the company?
The Skill marks them Departed, shows the move date from the signal, and returns the new employer and title where Lusha has them, with the verified email at the new company rather than the dead one. It then offers to find who holds the old seat now. For the full workflow on a departed champion, see Write the outreach when a contact changes jobs.
What does the tenure signal tell me?
How long the person has held the current role. Under six months is flagged Recent hire: new leaders tend to review the tools and vendors they inherited in their first quarter, so it’s a receptive window and worth leading with. Long tenure means an established relationship with the incumbent vendor, and the opener should respect that.
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.
