email-finder
email-finder
The output is one verified work email — not a list of guesses. Sending to a guess burns the address (bounces hurt the sender domain's reputation; agentmail SES isn't infinite). If you can't reach high confidence on the address, don't send — fall back to a different surface (LinkedIn DM, GitHub issue, Twitter @-mention) or skip the target.
The workflow is always: find candidates → verify → send. Skip the verify step and you're back to guessing.
What input do you have?
The cheapest method depends on what you start with. Pick the highest row that fits:
| Input you have | Cheapest first move |
|---|---|
| GitHub handle | git log --format="%ae" → unique on a clone of any repo they push to (see Method 1) |
| LinkedIn profile URL | Crustdata person/enrich?linkedin_profile_url=... (Method 6) — single API call returns work email if available |
| Personal site / portfolio URL | curl + grep -E '[A-Za-z0-9._-]+@[A-Za-z0-9.-]+' for emails on the page itself or in the HTML source (often hidden but not encoded) |
| Conference/event speaker | The event's published speakers/program page often lists the email or the company; combine with Method 4 |
| Just a name + company | Permutator + verifier (Method 4); if company has 50+ employees, likely Apollo or Hunter is faster |
| Just a name | Stop. Find them somewhere first (LinkedIn, GitHub, Twitter, their company's team page). A name alone is too sparse. |
More from kiluazen/skills
outreach
How to write cold messages, posts, and replies. Voice, tone, and style rules for all outbound communication — email, Reddit, HN, Twitter, LinkedIn.
8plumcake
Flag a systemic blocker to the human running you — a missing credential, a dead browser session, an API gate you can't get past. Things you can't fix from inside the sandbox. Not for asking permission or chatting; only for "hey, this is broken at the system level, I need you to fix it so I (and your other agents) stop hitting it.
8autark
Autark — running a market-discovery loop for a product, posting outreach, and recording it. Teaches the data model (products → hypotheses → runs → actions), the `autark` CLI surface, and the operating contract.
7email
Use when an agent needs to sign up for a service, log into a site, receive verification emails, or send outreach via the user's autark-provisioned AgentMail inbox.
7chrome-relay
Use when an agent needs to operate the user's real Chrome session — listing tabs, reading interactive elements, clicking, filling, typing into rich editors, pressing keys, evaluating JS, and capturing screenshots. All actions go through CDP and run on backgrounded tabs without stealing focus.
7