Apollo

Skill 89 of 200

Enrich Lead

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.

1 minute · 276 words · 6 sections

Install

$ npx skills add anthropics/knowledge-work-plugins --skill enrich-lead

$ npx skills add anthropics/knowledge-work-plugins

» /plugin marketplace add anthropics/knowledge-work-plugins

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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

Field	Detail
Email (work)	…
Email (personal)	… (if revealed)
Phone (direct)	…
Phone (mobile)	…
Phone (corporate)	…
Location	City, State, Country
LinkedIn	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_create with run_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_search with q_organization_domains_list set to this company
Find similar people — Search for people with the same title/seniority at other companies

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/knowledge-work-plugins, branch main, last pushed 23 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 27 distinct layouts observed: bio-research/skills/*/SKILL.md, cowork-plugin-management/skills/*/SKILL.md, customer-support/skills/*/SKILL.md, data/skills/*/SKILL.md, design/skills/*/SKILL.md, engineering/skills/*/SKILL.md, enterprise-search/skills/*/SKILL.md, finance/skills/*/SKILL.md, human-resources/skills/*/SKILL.md, legal/skills/*/SKILL.md, marketing/skills/*/SKILL.md, operations/skills/*/SKILL.md, partner-built/apollo/skills/*/SKILL.md, partner-built/brand-voice/skills/*/SKILL.md, partner-built/common-room/skills/*/SKILL.md, partner-built/slack/skills/*/SKILL.md, partner-built/zoom-plugin/skills/*/SKILL.md, partner-built/zoom-plugin/skills/contact-center/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/web/*/SKILL.md, partner-built/zoom-plugin/skills/video-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/virtual-agent/*/SKILL.md, partner-built/zoom-plugin/skills/zoom-mcp/*/SKILL.md, pdf-viewer/skills/*/SKILL.md, product-management/skills/*/SKILL.md, productivity/skills/*/SKILL.md, sales/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Enrich Lead”, a leading h1 that duplicated the skill title.

Spec compliance

53 editorial notes across 41 of 200 skills. They are printed in the margin of each skill rather than as errors here.

and 31 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Anthropic, declaring 120 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/knowledge-work-plugins.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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)

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

Field	Detail
Email (work)	…
Email (personal)	… (if revealed)
Phone (direct)	…
Phone (mobile)	…
Phone (corporate)	…
Location	City, State, Country
LinkedIn	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_create with run_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_search with q_organization_domains_list set to this company
Find similar people — Search for people with the same title/seniority at other companies