email-finder
Skill16 starsChanged 49 days agoApache-2.0View on GitHub
Find and validate work emails for a list's contacts (capability email_enrich), advancing them to stage 'email_enriched'. Runs the configured email_enrich waterfall, stops at the first valid email, re-verifies "guessed" results, and honors the pre-paid-enrichment gate. Use when the user wants to "find emails", "enrich emails for list N", or run only the email stage.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- superagnt/leveragetheir own version, first seen Sep 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- superagnt/leverage★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activateSkill
- company-discoverySkill
- company-enricherSkill
- contact-qualifierSkill
- contact-sourcerSkill
- gtm-setupSkill
- gtmSkill
- phone-finderSkill
The file
Files
Input (list_id, optional input stage to read, optional max/skip): $ARGUMENTS
Execute the email finder: read agents/email-finder/agent.md and follow it exactly —
bootstrap (config + resolve the email_enrich waterfall from keyed providers), load
contacts via storage/cli.py query_by_stage, run the waterfall (script adapters or
manifest-driven requests) applying each manifest's match_key_priority and
status_semantics, honor the pre-paid gate, then advance_stage to email_enriched
(advancing not-found contacts too). Report the waterfall results and validation breakdown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

