Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component...
npx skills add shipshitdev/library --skill "email-finder"
Install specific skill from multi-skill repository
# 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.
# 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:
[email protected][email protected][email protected][email protected]
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
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.