email-finder

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "email-finder" with this command: npx skills add shipshitdev/library/shipshitdev-library-email-finder

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:

  1. Check for existing email discovery tools
  2. Review available API keys (Hunter.io, Apollo.io)
  3. Check compliance/privacy requirements
  4. Look for project-specific [project]-email-finder skill

Methodology

Free Methods (Primary)

  1. Web Scraping - Scan /contact, /about, /team pages for emails
  2. WHOIS Lookup - Query domain registration data
  3. Pattern Guessing - Generate patterns from names found on site:
    • firstname.lastname@domain.com
    • firstnamelastname@domain.com
    • firstname@domain.com
    • f.lastname@domain.com

API Methods (If Keys Available)

APIEnv VariablePurpose
Hunter.ioHUNTER_API_KEYDomain search + verification
Apollo.ioAPOLLO_API_KEYContact discovery
Snov.ioSNOV_CLIENT_ID/SECRETEmail finder
ClearbitCLEARBIT_API_KEYCompany 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 companies
  • copywriter - Use found emails for outreach campaigns

For complete implementation code, API examples, verification patterns, and rate limiting utilities, see: references/full-guide.md

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

financial-operations-expert

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

youtube-video-analyst

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

nestjs-testing-expert

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

brand-name-generator

No summary provided by upstream source.

Repository SourceNeeds Review