enrich-lead
Skill25 starsChanged 4 months agoMITView on GitHub
Instant lead enrichment. Drop a name, company, LinkedIn URL, or email and get the full contact card with email, phone, title, company intel, and next actions.
4 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- firecrawl/firecrawl-claude-plugintheir own version, first seen Nov 1, 2026
- Rajveerx11/skillstheir own version, first seen Oct 25, 2026
- anthropics/knowledge-work-pluginsedited, first seen Oct 13, 2026
- edu6565/claude-skillsedited, first seen Oct 11, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- anthropics/knowledge-work-plugins★ 36k100% same
- edu6565/claude-skills★ 0100% same
Wrote their own version · 2
- firecrawl/firecrawl-claude-plugin★ 261same name
- Rajveerx11/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- analyticsSkill
- gtm-strategistSkill
- prospectSkill
- sequence-loadSkill
The file
We split this skill into the rules it gives an agent
5 rules. 1 is common, 0 are distinctive, and 4 are very specific to this project.
1
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If the input is ambiguous (e.g.
- Very specific: line 35
Use mcp__claude_ai_Apollo_MCP__apollo_people_match with all available identifiers:
- Very specific: line 42
If the match fails, try mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with looser filters and present the top 3 candidates.
- Very specific: line 46
Use mcp__claude_ai_Apollo_MCP__apollo_organizations_enrich with the person's company domain to pull firmographic context.
- Common: line 75
Ask the user which action to take:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Enrich Lead
Turn any identifier into a full contact dossier. The user provides identifying info via "$ARGUMENTS".
Examples
/apollo:enrich-lead Tim Zheng at Apollo/apollo:enrich-lead https://www.linkedin.com/in/timzheng/apollo:enrich-lead sarah@stripe.com/apollo:enrich-lead Jane Smith, VP Engineering, Notion/apollo:enrich-lead CEO of Figma
Step 1 — Parse Input
From "$ARGUMENTS", extract every identifier available:
- First name, last name
- Company name or domain
- LinkedIn URL
- Email address
- Job title (use as a matching hint)
If the input is ambiguous (e.g. just "CEO of Figma"), first use mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with relevant title and domain filters to identify the person, then proceed to enrichment.
Step 2 — Enrich the Person
Credit warning: Tell the user enrichment consumes 1 Apollo credit before calling.
Use mcp__claude_ai_Apollo_MCP__apollo_people_match with all available identifiers:
first_name,last_nameif name is knowndomainororganization_nameif company is knownlinkedin_urlif LinkedIn is providedemailif email is provided- Set
reveal_personal_emailstotrue
If the match fails, try mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with looser filters and present the top 3 candidates. Ask the user to pick one, then re-enrich.
Step 3 — Enrich Their Company
Use mcp__claude_ai_Apollo_MCP__apollo_organizations_enrich with the person's company domain to pull firmographic context.
Step 4 — Present the Contact Card
Format the output exactly like this:
[Full Name] | [Title] [Company Name] · [Industry] · [Employee Count] employees
| Field | Detail |
| Email (work) | ... |
| Email (personal) | ... (if revealed) |
| Phone (direct) | ... |
| Phone (mobile) | ... |
| Phone (corporate) | ... |
| Location | City, State, Country |
| URL | |
| Company Domain | ... |
| Company Revenue | Range |
| Company Funding | Total raised |
| Company HQ | Location |
Step 5 — Offer Next Actions
Ask the user which action to take:
- Save to Apollo — Create this person as a contact via
mcp__claude_ai_Apollo_MCP__apollo_contacts_createwithrun_dedupe: true - Add to a sequence — Ask which sequence, then run the sequence-load flow
- Find colleagues — Search for more people at the same company using
mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_searchwithq_organization_domains_listset to this company - Find similar people — Search for people with the same title/seniority at other companies
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

