
Contact Hunter
- 356 installs
- 237 repo stars
- Updated July 15, 2026
- onewave-ai/claude-skills
contact-hunter is a Claude Code research skill that finds and validates publicly available contact information for leads using structured search plans and CRM-ready export formats.
About
contact-hunter is a guided research skill from onewave-ai/claude-skills that helps developers and revenue engineers find, verify, and enrich contact details without directly calling paid APIs. The skill classifies searches as person, company, role, email verification, or bulk enrichment, then collects parameters like name, company, title, location, LinkedIn URL, and email domain. It recommends source-specific queries for LinkedIn, company About/Team pages, GitHub profiles, Twitter/X, professional directories, and optional paid tools the user already owns such as Hunter.io, Apollo.io, ZoomInfo, or RocketReach. Results are formatted into contact cards with source attribution and confidence levels, exportable as CSV, JSON, or vCard for CRM import. Developers reach for contact-hunter when building prospect lists, validating inbound leads, or enriching existing CRM records through a repeatable manual-plus-guided workflow.
- Claude Code skill
- Agent capability extension
- Developer productivity
- Workflow automation
- Easy integration
Contact Hunter by the numbers
- 356 all-time installs (skills.sh)
- +6 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #2,126 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill contact-hunterAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 356 |
|---|---|
| repo stars | ★ 237 |
| Last updated | July 15, 2026 |
| Repository | onewave-ai/claude-skills ↗ |
How do you find verified B2B contact emails?
Finds and validates contact information for leads and prospects from publicly available sources.
Who is it for?
Developers supporting sales or recruiting workflows who need guided public-source contact research with attribution and export formatting.
Skip if: Teams requiring fully automated paid API enrichment without manual verification or compliance review of public data sources.
When should I use this skill?
User needs to find, verify, or enrich contact information for a person, company, role, or bulk prospect list from public sources.
What you get
Contact cards with source attribution, confidence levels, and CSV, JSON, or vCard exports for CRM import.
- Contact cards with attribution
- CSV or JSON export
- Per-target search query plan
By the numbers
- Parent onewave-ai/claude-skills repository ships 172 production-ready skills
- Exports contact results as CSV, JSON, or vCard
Files
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 patternsreferences/output-templates.md— data collection template, contact card, bulk CSV, email-pattern report, export formatsreferences/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"
Compliance and Ethics
This skill guides discovery of publicly available contact information only. Apply these rules to every search and result.
Allowed
- Publicly available information
- Business contact information
- LinkedIn public profiles
- Company websites
- Professional directories
- Published contact lists
Not allowed
- Scraping private databases
- Purchasing questionable contact lists
- Bypassing email verification
- Ignoring opt-out requests
- Violating GDPR/CCPA
- Harassing contacts
Best practices
- Always cite data sources
- Respect privacy and do-not-contact preferences
- Use for legitimate business purposes only
- Keep data current and note freshness
- Provide opt-out mechanisms
- Follow CAN-SPAM for cold outreach
- Comply with applicable data protection laws
Verification steps
1. Cross-reference multiple sources 2. Confirm the LinkedIn profile matches the company 3. Verify the email format matches the company pattern 4. Validate phone number format 5. Confirm the job title is current 6. Check for recent company changes
Output Templates
Fill these once contact data is found. Cite every source and note verification date.
Data collection template
Full Name: [First Last]
Job Title: [Exact title]
Company: [Company name]
Email: [email@domain.com]
Phone: [(xxx) xxx-xxxx]
LinkedIn: [linkedin.com/in/username]
Location: [City, State/Country]
Department: [Engineering, Sales, etc.]
Additional Info:
- Reports to: [Manager name]
- Team size: [Number]
- Start date: [When they joined]
- Previous companies: [List]
- Education: [Degree, School]
Data Sources:
- [LinkedIn profile URL]
- [Company website URL]
- [Other sources]Individual contact card
+-------------------------------------------+
| JOHN SMITH |
| VP of Engineering @ Acme Corp |
+-------------------------------------------+
| Email: john.smith@acme.com |
| Phone: (415) 555-0123 |
| LinkedIn: linkedin.com/in/johnsmith |
| Location: San Francisco, CA |
+-------------------------------------------+
| Department: Engineering |
| Reports to: Sarah Chen (CTO) |
| Team size: ~45 engineers |
| Tenure: 2+ years at Acme |
+-------------------------------------------+
| Sources: |
| - LinkedIn (verified) |
| - Company website |
| - Verified: 2024-01-15 |
+-------------------------------------------+Bulk results (CSV)
Name,Title,Company,Email,Phone,LinkedIn,Location,Source,Verified
John Smith,VP Engineering,Acme Corp,john.smith@acme.com,(415) 555-0123,linkedin.com/in/johnsmith,San Francisco,LinkedIn,2024-01-15
Jane Doe,Director Marketing,Acme Corp,jane.doe@acme.com,(415) 555-0124,linkedin.com/in/janedoe,San Francisco,Company Website,2024-01-15Email pattern report
DETECTED EMAIL PATTERN: Acme Corp
Confirmed emails found:
- john.smith@acme.com
- sarah.chen@acme.com
- michael.jones@acme.com
Detected pattern: firstname.lastname@acme.com
Confidence: 95%
Alternative patterns (if primary fails):
- firstname@acme.com
- firstnamelastname@acme.com
- f.lastname@acme.com
To verify an unknown email:
1. Use an email verification tool
2. Check for bounce/invalid response
3. Inspect SMTP response
4. Cross-check on LinkedInExport formats
- CSV: for generic CRM import
- JSON: for API integration
- vCard: for contact managers
- Salesforce CSV: pre-formatted for SFDC
- HubSpot CSV: pre-formatted for HubSpot
Search Query Templates
Use these query patterns once search parameters (name, company, title, location, domain) are gathered. Replace bracketed values.
Per-target search brief
Format the search plan as follows for a single target (example: John Smith, VP of Engineering, Acme Corp, San Francisco):
Search parameters
- Target: John Smith
- Company: Acme Corp
- Title: VP of Engineering
- Location: San Francisco, CA
Recommended queries
LinkedIn: 1. Search: "John Smith VP Engineering Acme Corp" 2. Apply company filter: "Acme Corp" 3. Apply title filter: "VP of Engineering" 4. Apply location: "San Francisco Bay Area"
Google: 1. "John Smith" "VP of Engineering" "Acme Corp" 2. "John Smith" "Acme Corp" email 3. site:linkedin.com/in "John Smith" "Acme" 4. site:acme.com "John Smith"
Company website: 1. https://acme.com/about 2. https://acme.com/team 3. https://acme.com/leadership 4. https://acme.com/contact
Email pattern candidates at acme.com:
- john.smith@acme.com
- john@acme.com
- jsmith@acme.com
- j.smith@acme.com
- smithj@acme.com
GitHub (technical roles):
- Search: "John Smith Acme"
- Inspect bio for company affiliation
Reusable query patterns
For company employees:
site:linkedin.com/in "[Company Name]"
OR
site:[company-domain.com] "team" OR "about" OR "leadership"For specific roles:
"[Job Title]" "[Company]" email
OR
"[Job Title]" site:linkedin.com "[Company]"For email validation:
- Check company website for email format
- Use an email verification service
- Look for the pattern in existing confirmed emails
- Test with email finder tools
For phone numbers:
- Company website contact page
- LinkedIn profile (when public)
- Professional directories
- Industry associations
Related skills
How it compares
Pick contact-hunter for guided public-source research with attribution when you lack automated API enrichment budgets or need human-verified contact cards.
FAQ
Does contact-hunter call paid enrichment APIs directly?
contact-hunter does not call paid APIs directly. The skill produces structured search queries, recommends public and professional sources, and formats verified results. Users with Hunter.io, Apollo.io, or ZoomInfo access run those tools separately.
What export formats does contact-hunter support?
contact-hunter formats results into individual contact cards exportable as CSV, JSON, or vCard. Each record includes source attribution and confidence levels suitable for CRM import or outreach tooling.
What search types does contact-hunter handle?
contact-hunter supports person, company, role-based, email verification, and bulk enrichment modes. It gathers parameters like name, company, title, location, LinkedIn URL, and email domain before building per-target search plans.