From career
Find the right person to contact at a target company using Hunter.io. Use when the user needs decision-maker / hiring-manager / founder contact details before drafting an outreach. Returns ranked candidates with confidence scores; optionally appends to the workspace CRM. Hunter MCP is required.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin careerThis skill is limited to using the following tools:
Hunter.io wrapper. Finds people at a target company and returns ranked candidates the user can pass into `draft-outreach`.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Hunter.io wrapper. Finds people at a target company and returns ranked candidates the user can pass into draft-outreach.
$ARGUMENTS:
<company> — name or domain. First positional.--role=<filter> — e.g. engineering manager, founder, head of product. Filters Hunter results by department/seniority.--n=<count> (default 5) — max candidates to return.--append-to-crm — write rows into crm/companies.md.--lens=<employer|client|partner> — sets the CRM row's lens column (default employer)./career:outreach find acme.com
/career:outreach find snowglobe.ai --role="head of platform" --n=3
/career:outreach find myrofish --role=founder --append-to-crm
${CAREER_DATA_DIR}/config.json → WORKING_FOLDER. If companions.email is false, warn the user that send-outreach won't work yet — find-contact can still proceed.
If <company> looks like a domain (*.tld), use directly.
Otherwise, use Hunter Company-Enrichment (or Combined-Enrichment if a contact name is also implied) to resolve company name → primary domain.
If Hunter returns multiple candidate domains, ask the user which one.
Domain-Search with the resolved domain. Apply role / department filter from --role.
Limit to --n results. Hunter returns confidence scores — pass through.
For the top --n results:
Email-Verifier to check deliverability — adds a verified flag.Output a markdown table to the user:
| rank | name | role | email | confidence | verified | source |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | ... | ... | ... | 92 | yes | hunter |
Include a "next step" hint:
To draft outreach to one of these:
/career:outreach draft <company> --contact-rank=1 --template=cold-pitch
If --append-to-crm:
For each contact, ensure ${WORKING_FOLDER}/crm/companies.md has a row for the company (lens, status watching, last-touch today). The contacts table itself lives in the brief output; the CRM row is per-company, not per-contact.
For each contact, ensure ${WORKING_FOLDER}/crm/contacts.md exists; create with header if not:
| company-slug | name | role | email | confidence | verified | last-touch | notes |
Then append a row per contact.
send-outreach with explicit confirm.hunter MCP via the personal MCP catalog or op-vault.--append-to-crm is upsert: existing rows are updated by name + email, not duplicated.