shipshitdev/email-finder
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.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library email-finderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:41 AM137.3s3 files scanned
SKILL.md
- name:
- email-finder
- description:
- 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.
- version:
- 1.0.0
- tags:
- email, domain, contact-discovery, lead-generation
Email Finder
Overview
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.
When to Use
- Scan a domain to find associated emails
- Find contact emails for a company
- Replace email hunter functionality
- Find email patterns for a domain
- Verify email addresses
- Enrich contact data with discovered emails
Project Context Discovery
Before finding emails:
- Check for existing email discovery tools
- Review available API keys (Hunter.io, Apollo.io)
- Check compliance/privacy requirements
- Look for project-specific
[project]-email-finderskill
Methodology
Free Methods (Primary)
- Web Scraping - Scan
/contact,/about,/teampages for emails - WHOIS Lookup - Query domain registration data
- Pattern Guessing - Generate patterns from names found on site:
API Methods (If Keys Available)
| 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 |
Email Result Interface
interface EmailResult {
email: string;
source: 'web-scraping' | 'whois' | 'pattern-guessing' | 'hunter' | 'apollo';
confidence?: number;
firstName?: string;
lastName?: string;
position?: string;
verified?: boolean;
}
Best Practices
- Rate limiting: Delay between requests (1s recommended)
- Respect robots.txt: Check before scraping
- Deduplicate: Normalize emails (lowercase, trim)
- Verify: Use MX record checks or API verification
- Filter: Remove noreply@, donotreply@ addresses
Legal & Ethical
- Comply with GDPR/CCPA
- Respect terms of service
- Honor opt-out requests
- Don't spam discovered emails
Integration
Works well with:
leads-researcher- Discover contact emails after researching companiescopywriter- Use found emails for outreach campaigns
For complete implementation code, API examples, verification patterns, and rate limiting utilities, see: references/full-guide.md
Related Skills
shipshitdev/worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.
27SKILL.mdUpdated Jun 13, 2026