Hunter Automation
Automate Hunter.io email intelligence -- search domains for email addresses, find specific contacts, verify email deliverability, manage leads, and monitor account usage -- using natural language through the Composio MCP integration.
Get the complete skill folder, including its scripts and reference files.
This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.
When to use this skill
Use Hunter Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Hunter.io email intelligence -- search domains for email addresses, find specific contacts, verify email deliverability, manage leads, and monitor account usage -- using natural language through the Composio MCP integration.
When not to use it
Skip Hunter Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/hunter-automation # Save SKILL.md to ~/.claude/skills/hunter-automation/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/hunter-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/hunter-automation/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Hunter Automation skill for this task: Use Hunter Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
63/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 67/100
- Practical detail
- 50/100
- Source evidence
- 63/100
- Source signals
- 80/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Hunter Automation
Power your outreach with Hunter.io -- discover email addresses by domain, find specific people's emails, verify deliverability, save leads, and track your API usage -- all through natural language commands.
**Toolkit docs:** [composio.dev/toolkits/hunter](https://composio.dev/toolkits/hunter)
---
## Setup
1. Add the Composio MCP server to your client configuration: ``` https://rube.app/mcp ``` 2. Connect your Hunter.io account when prompted (API key authentication). 3. Start issuing natural language commands to find and verify emails.
---
## Core Workflows
### 1. Search Domain for Email Addresses Discover all publicly available email addresses for a given domain or company, with filtering by department, seniority, and type.
**Tool:** `HUNTER_DOMAIN_SEARCH`
**Example prompt:** > "Find all executive email addresses at stripe.com using Hunter"
**Key parameters:** - `domain` -- Domain to search (e.g., "stripe.com"). Required if `company` not provided. - `company` -- Company name to search (e.g., "Stripe"). Required if `domain` not provided. - `type` -- Filter by "personal" or "generic" emails - `seniority` -- Filter by levels: "junior", "senior", "executive" (array) - `department` -- Filter by departments: "executive", "it", "finance", "sales", etc. (array) - `required_field` -- Require specific fields: "full_name", "position", "phone_number" (array) - `limit` -- Max results per request (1-100, default 10; free/basic plans limited to 10) - `offset` -- Skip results for pagination (default 0)
---
### 2. Find a Specific Person's Email Infer the most likely email address for a person given their name and domain or company.
**Tool:** `HUNTER_EMAIL_FINDER`
**Example prompt:** > "Find the email for Alexis Ohanian at reddit.com using Hunter"
**Key parameters:** - `domain` -- Target domain (e.g., "reddit.com"). Takes precedence over `company`. - `company` -- Company name (e.g., "Reddit"). Used if domain not provided. - Name (one of these combinations required): - `first_name` + `last_name` (e.g., "Alexis" + "Ohanian") - `full_name` (e.g., "Alexis Ohanian") - `max_duration` -- Max request duration in seconds (3-20, default 10). Longer durations yield more accurate results.
---
### 3. Verify Email Deliverability Check whether an email address is valid, deliverable, and safe to send to.
**Tool:** `HUNTER_EMAIL_VERIFIER`
**Example prompt:** > "Verify if [email protected] is a valid email address"
**Key parameters:** - `email` (required) -- The email address to verify (e.g., "[email protected]")
**Response includes:** verification status, deliverability score, MX record validation, and risk assessment.
---
### 4. Get Email Volume Estimates Check how many email addresses Hunter has for a domain or company -- this call is free and does not consume API credits.
**Tool:** `HUNTER_EMAIL_COUNT`
**Example prompt:** > "How many email addresses does Hunter have for stripe.com?"
**Key parameters:** - `domain` -- Domain to query (e.g., "stripe.com"). Required if `company` not provided. - `company` -- Company name (min 3 characters). Required if `domain` not provided. - `type` -- Filter count by "personal" or "generic" emails
**Returns:** Total count with breakdowns by type, department, and seniority level.
---
### 5. Save and Manage Leads Create or update leads by email in a single upsert call -- no need to check existence first.
**Tool:** `HUNTER_UPSERT_LEAD`
**Example prompt:** > "Save [email protected] as a lead in Hunter with name John Doe, position CTO"
**Key parameters:** - `email` -- Lead's email address (primary identifier for upsert) - Name, position, company, and other lead metadata
---
### 6. Check Account Usage and Limits Review your Hunter account plan details, remaining searches, and verification quotas before running bulk operations.
**Tool:** `HUNTER_ACCOUNT_INFORMATION`
**Example prompt:** > "How many Hunter API searches do I have left this month?"
**Key parameters:** None required.
---
## Known Pitfalls
- **HTTP 401 means invalid credentials**: `authentication_failed` errors indicate an invalid or expired API key. Fix before attempting bulk operations. - **Email counts are estimates**: `HUNTER_EMAIL_COUNT` returns approximate numbers for sizing and prioritization, not guaranteed retrievable email counts. - **Domain search uses offset pagination**: `HUNTER_DOMAIN_SEARCH` paginates via `limit`/`offset`. Do not assume the first page is complete -- continue fetching until results are empty or you hit a cap. - **Empty results are not errors**: `HUNTER_DOMAIN_SEARCH` can return `emails: []` with no error. Treat as "no data found" and continue, rather than retrying as a failure. - **Verification status nuances**: `accept_all` or `risky` statuses from `HUNTER_EMAIL_VERIFIER` indicate uncertainty. Exclude these from strict deliverability workflows or handle them separately. - **Free/basic plan limits**: Free and basic plans limit `HUNTER_DOMAIN_SEARCH` to 10 results per request. Higher limits require a paid plan. - **Domain format matters**: Use bare domains like "stripe.com" -- do not include protocol ("https://") or "www." prefix.
---
## Quick Reference
| Action | Tool Slug | Required Params | |---|---|---| | Search domain emails | `HUNTER_DOMAIN_SEARCH` | `domain` or `company` | | Find person's email | `HUNTER_EMAIL_FINDER` | Name + (`domain` or `company`) | | Verify email | `HUNTER_EMAIL_VERIFIER` | `email` | | Get email count | `HUNTER_EMAIL_COUNT` | `domain` or `company` | | Save/update lead | `HUNTER_UPSERT_LEAD` | `email` | | Check account | `HUNTER_ACCOUNT_INFORMATION` | None |
---
*Powered by [Composio](https://composio.dev)*
Intended uses
- Use Hunter Automation when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.