Skip to content
Agentmart
Submit a tool

contact-lookup

Find, validate, or identify one B2B contact with LeadMagic MCP — work email, profile, or reverse email lookup.

Skill by LeadMagic

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/leadmagic-contact-lookup

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Find, validate, or identify one B2B contact with LeadMagic MCP — work email, profile, or reverse email lookup. Use when the user has a person plus company, a profile URL, or an email and wants a work email, deliverability check, or who-is-this answer.

Use cases: productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/contact-lookup

What's inside

Skill name
contact-lookup
Description
Find, validate, or identify one B2B contact with LeadMagic MCP — work email, profile, or reverse email lookup. Use when the user has a person plus company, a profile URL, or an email and wants a work email, deliverability check, or who-is-this answer.
License
MIT
Instructions
27 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Contact lookup

## Trigger
Use when the user needs a work email for a specific person, wants to check an address, or wants the professional profile behind a URL or email. For more than 5 people, use the `bulk-enrichment` or `sheets` skill — never loop these tools per row.

## Workflow
1. Start from the strongest identifier the user gave:
   - Existing email from elsewhere (CRM, list, sign-up) → `validate_work_email`. Its public status is exactly `valid`, `invalid`, or `unknown`; treat only `valid` as deliverable. `unknown` includes catch-all results and must never be reported as deliverable.
   - Full name + company/domain → `find_work_email`, or composite `enrich_contact` when they want the full picture
   - Profile URL (the full URL; the path ends in `in/{slug}`) → `b2b_profile_to_work_email` for the work email, `search_profile` for name, role, company, and work history
   - Email only, and they want the person behind it → `email_to_b2b_profile` (returns a profile URL), then `search_profile` if they want details
   - "Has this person moved on?" → `detect_job_change` with `profile_url` (most reliable) or `work_email`, plus the expected company when known
2. Take the cheapest path that answers the question:
   - Do not re-find an email that already validates.
   - Never validate an email a LeadMagic finder just returned: finder emails are already validated. For any validation result, only the exact status `valid` is a success; `invalid` and `unknown` are not. Do not present catch-all/unknown results as deliverable.
   - Use `email_to_b2b_profile` only when the user actually needs the profile. It is pricier than the email tools, so check `preview_cost` first.
3. Prefer one composite over chaining many primitives, and don't repeat a lookup already made for the same inputs.
4. Personal email (`find_personal_email`) and mobile (`find_mobile_number`) are lawful B2B fallbacks. Use them only when the user explicitly asks for that channel.
5. Report only fields the tools returned — never invent contacts, emails, or titles.

## Output
- The best contact field found and its validation status
- The inputs used and the tools called
- Not-found cases (usually free)
- A concise next action

From LeadMagic/leadmagic-claude-plugin, MIT.

More from LeadMagic/leadmagic-claude-plugin

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Oct 12, 2026 (16 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from LeadMagic

Cite this page

contact-lookup skill. Agent Mart. https://agentmart.dev/skills/leadmagic-contact-lookup (last updated 2026-10-24)