agentleFS
apolloioapolloio/apollo-mcp-plugin/skills/enrich-lead/SKILL.md

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

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 2

    1. anthropics/knowledge-work-plugins★ 36k100% same
    2. edu6565/claude-skills★ 0100% same

    Wrote their own version · 2

    1. firecrawl/firecrawl-claude-plugin★ 261same name
    2. 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.

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
  1. Very specific:

    If the input is ambiguous (e.g.

    line 29
  2. Very specific:

    Use mcp__claude_ai_Apollo_MCP__apollo_people_match with all available identifiers:

    line 35
  3. Very specific:

    If the match fails, try mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with looser filters and present the top 3 candidates.

    line 42
  4. Very specific:

    Use mcp__claude_ai_Apollo_MCP__apollo_organizations_enrich with the person's company domain to pull firmographic context.

    line 46
  5. Common:

    Ask the user which action to take:

    line 75

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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_name if name is known
  • domain or organization_name if company is known
  • linkedin_url if LinkedIn is provided
  • email if email is provided
  • Set reveal_personal_emails to true

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

FieldDetail
Email (work)...
Email (personal)... (if revealed)
Phone (direct)...
Phone (mobile)...
Phone (corporate)...
LocationCity, State, Country
LinkedInURL
Company Domain...
Company RevenueRange
Company FundingTotal raised
Company HQLocation

Step 5 — Offer Next Actions

Ask the user which action to take:

  1. Save to Apollo — Create this person as a contact via mcp__claude_ai_Apollo_MCP__apollo_contacts_create with run_dedupe: true
  2. Add to a sequence — Ask which sequence, then run the sequence-load flow
  3. Find colleagues — Search for more people at the same company using mcp__claude_ai_Apollo_MCP__apollo_mixed_people_api_search with q_organization_domains_list set to this company
  4. Find similar people — Search for people with the same title/seniority at other companies

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.