bundles/sales/skills/email-finder/SKILL.md
This skill should be used when users need to find email addresses associated with a domain. It activates when users ask to scan a domain for emails, find contact emails, discover email addresses, or replace email hunter functionality.
npx skillsauth add shipshitdev/library email-finderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Discover email addresses associated with a domain using a hybrid approach: free methods first (web scraping, pattern guessing, WHOIS lookup), then APIs (Hunter.io, Apollo.io, etc.) when keys are available.
Before finding emails:
[project]-email-finder skill/contact, /about, /team pages for emails| API | Env Variable | Purpose |
|-----|-------------|---------|
| Hunter.io | HUNTER_API_KEY | Domain search + verification |
| Apollo.io | APOLLO_API_KEY | Contact discovery |
| Snov.io | SNOV_CLIENT_ID/SECRET | Email finder |
| Clearbit | CLEARBIT_API_KEY | Company enrichment |
interface EmailResult {
email: string;
source: 'web-scraping' | 'whois' | 'pattern-guessing' | 'hunter' | 'apollo';
confidence?: number;
firstName?: string;
lastName?: string;
position?: string;
verified?: boolean;
}
Works well with:
leads-researcher - Discover contact emails after researching companiescopywriter - Use found emails for outreach campaignsFor complete implementation code, API examples, verification patterns, and rate limiting utilities, see: references/full-guide.md
development
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.