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
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
tools
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
tools
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
tools
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.