agentleFS
OneWave-AIOneWave-AI/claude-skills/contact-hunter/SKILL.md

contact-hunter

Skill378 starsChanged 52 days agoMITView on GitHub

Search and extract contact information for people or companies including names, phone numbers, emails, job titles, and LinkedIn profiles. Aggregates data from multiple sources and provides enriched contact details. Use when users need to find contact information, build prospect lists, or enrich existing contact data.

The file

Files
SKILL.md

Contact Hunter

Find and enrich publicly available contact information from multiple sources with full source attribution.

This skill guides the search process and organizes results. It does not directly access paid APIs; it produces structured queries, suggests where to look, then validates and formats what is found.

Contents

  • references/search-queries.md — per-target search briefs and reusable query patterns
  • references/output-templates.md — data collection template, contact card, bulk CSV, email-pattern report, export formats
  • references/compliance.md — allowed/not-allowed rules, best practices, verification steps

Workflow

  1. Identify the search type: person, company, role, email verification, or bulk enrichment.
  2. Gather search parameters: name, company, job title, location, industry, LinkedIn URL, email domain, and any other identifiers.
  3. Select sources to check: LinkedIn, company website (About/Team/Contact/Leadership), GitHub (developers), Twitter/X, professional directories, public databases, and any paid tools the user has access to (ZoomInfo, Apollo.io, Hunter.io, RocketReach).
  4. Build the search plan using the query patterns in references/search-queries.md. Produce a per-target brief with LinkedIn, Google, company-website, email-pattern, and GitHub queries.
  5. Detect the company email pattern from confirmed addresses, then derive candidate emails. See the email-pattern report in references/output-templates.md.
  6. Collect and verify results. Cross-reference multiple sources and run the verification steps in references/compliance.md before recording any field.
  7. Format output using the templates in references/output-templates.md: data collection template, individual contact card, or bulk CSV. Export as CSV, JSON, vCard, or CRM-specific CSV (Salesforce, HubSpot) as requested.
  8. For enrichment of existing contacts, refresh: current job title, company changes, updated contact info, social profiles, company information, reporting structure, and recent activity.

Quality bar

Ensure every contact record includes all available fields, cites its sources, carries a confidence/verification level and freshness date, follows data-privacy law, is formatted consistently, notes contact preferences, provides role context (tenure, team), flags uncertainties, and suggests verification steps. Operate only within the rules in references/compliance.md.

Example triggers

  • "Find the VP of Sales at Acme Corp"
  • "Get contact info for John Smith at Microsoft"
  • "Find engineering managers at Stripe"
  • "Enrich this list of contacts with emails"
  • "What's the email pattern at Google?"
  • "Find the marketing team at HubSpot"

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.