Agent skill
email-finder
Find and validate work emails for a list's contacts (capability email_enrich), advancing them to stage 'email_enriched'.
Filed under Prospecting and list building.
From kkrlstrm/gtm-pipeline · 9 skill entries · 16 · pushed 2026-09-29
What it does when it runs
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.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- Read
- Bash
- Actions present in the files
- shell
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/kkrlstrm/gtm-pipeline.git /tmp/gtm-pipeline git -C /tmp/gtm-pipeline sparse-checkout set ".claude/skills/email-finder" mkdir -p ~/.claude/skills/email-finder cp -R "/tmp/gtm-pipeline/.claude/skills/email-finder/." ~/.claude/skills/email-finder/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from kkrlstrm/gtm-pipeline/blob/3fdc07a14e4f3991eba66ec2e8a9feb8fec4a197/.claude/skills/email-finder/SKILL.md, which is licensed APACHE-2.0 (repository). 69 words, 0 headings.
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.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- cold-email by coreyhaines31 · 54,316
- citation-source-gap-finder by irinabuht12-oss · 4,293
- email-sequence-writer by irinabuht12-oss · 4,293
- wasted-spend-finder by irinabuht12-oss · 4,293
- cold-email-kickoff by growthenginenowoslawski · 759
- cold-email-starter-kit by growthenginenowoslawski · 759
- cold-email-weekly-rhythm by growthenginenowoslawski · 759
- email-deliverability-audit by growthenginenowoslawski · 759
Need help setting it up?
This page tells you what email-finder does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.