sales-hunter

name	sales-hunter
description	Hunter.io platform help — Domain Search, Email Finder, Email Verifier, Campaigns, Discover, Signals, TechLookup, Leads, browser extension, API, integrations, MCP server. Use when email addresses are bouncing, need to find emails for a domain, Hunter verification results seem wrong, campaign sequences aren't sending, Discover or Signals data looks incomplete, integrations aren't syncing, or API calls aren't returning expected data. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or enriching contacts across multiple tools (use /sales-enrich).
argument-hint	[describe what you need help with in Hunter.io]
license	MIT
version	1.0.1
tags	["sales","enrichment","email-finder","verification","platform"]
github	https://github.com/hunter-io

Hunter.io Platform Help

Help the user with Hunter.io platform questions — from finding and verifying emails through campaign setup, Discover, Signals, TechLookup, API, and integrations.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What area of Hunter.io do you need help with?

   • A) Domain Search — find all emails at a company
   • B) Email Finder — find a specific person's email
   • C) Email Verifier — verify email deliverability
   • D) Campaigns — cold email sequences and follow-ups
   • E) Discover — find companies by industry, size, location, technology
   • F) Signals — buying intent and company change alerts
   • G) TechLookup — find companies using specific technologies
   • H) Leads — managing lead lists
   • I) Browser Extension — finding emails while browsing
   • J) API — automation, integrations, programmatic access
   • K) Integrations — HubSpot, Salesforce, Pipedrive, Zapier, Google Sheets
   • L) Admin — billing, credits, plan features
   • M) Something else — describe it

2. What's your role?

   • A) Sales rep / AE / BDR
   • B) Sales manager / team lead
   • C) RevOps / Sales Ops
   • D) Marketer
   • E) Admin / IT
   • F) Founder / solo seller
   • G) Other

3. What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.

Step 2 — Route or answer directly

If the request maps to a specialized skill, route:

• List building / prospecting → /sales-prospect-list
• Contact enrichment / data hygiene → /sales-enrich
• Cadence strategy / sequence design → /sales-cadence
• Cross-platform deliverability → /sales-deliverability
• Tool integration architecture → /sales-integration