Systems Lab

Agent skill

email-waterfall

Set up email waterfall enrichment in Clay for maximum coverage.

slowingReaches the webInstructions only417 words

Filed under Prospecting and list building.

From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14

What it does when it runs

Set up email waterfall enrichment in Clay for maximum coverage. Use when the user asks about finding work emails, email enrichment, email waterfall setup, provider ordering, email coverage optimization, conditional runs for email, bounce rates, or email validation. Triggers on "find emails", "email waterfall", "email coverage", "email discovery", "work email", "email provider", "bounce rate". Do NOT use for phone enrichment, company-only enrichment without email needs, or general CRM email questions.

Read from 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
  • frontal.so
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about email-waterfall

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills
git -C /tmp/outbound-skills sparse-checkout set "master-skills/clay/.claude/skills/email-waterfall"
mkdir -p ~/.claude/skills/email-waterfall
cp -R "/tmp/outbound-skills/master-skills/clay/.claude/skills/email-waterfall/." ~/.claude/skills/email-waterfall/

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 Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/clay/.claude/skills/email-waterfall/SKILL.md, which is licensed MIT (repository). 417 words, 9 headings.

Email Waterfall Enrichment

You help users set up email waterfall enrichment in Clay to maximize coverage from ~40% (single provider) to 85%+ (waterfall).

Reference

Read {SKILL_BASE}/resources/waterfall-enrichment.md for full provider list, setup steps, and validation details.

Key Benchmarks

  • Single email finder: ~40% coverage
  • 4-provider waterfall: 70-80% coverage
  • 6-provider waterfall: 85%+ coverage
  • Target bounce rate: under 2%
  • Credits per provider attempt: 2-5 credits (refunded if not found)

Recommended Provider Order (Cheapest First)

  1. LeadMagic (2 credits)
  2. Prospeo (2 credits)
  3. Hunter (2 credits)
  4. Apollo (3 credits)
  5. RocketReach (3 credits)
  6. FindyMail (2 credits)

You only pay for providers actually used. If found at Provider 3, cost = 2+2+2 = 6 credits, not 14.

Required Inputs (Best to Worst)

  1. Best: Company Domain + LinkedIn Profile URL (highest match rate)
  2. Good: Company Domain + Full Name
  3. Fallback: Full Name + Company Name (lowest precision)

Setup Steps

  1. Click "Add enrichment" and search "Work Email"
  2. Select the waterfall enrichment type
  3. Reorder providers (cheapest first)
  4. Map input columns: domain, LinkedIn URL, full name
  5. Enable ZeroBounce validation (default)
  6. Add conditional run: "Only run if /email is empty"
  7. Test on 50 rows before running full table

Mandatory Conditional Run Formula

Always add this to avoid wasting credits on rows that already have emails:

/email is empty

For re-enrichment workflows (e.g., CRM cleanup), use:

/email is empty OR /email_validation equals "invalid"

Validation Step

After the waterfall, add a separate email verification column:

  • Primary: MillionVerifier (bulk, cheapest)
  • Backup: Clay native verification
  • Remove: invalid, disposable addresses
  • Flag: risky/catchall emails for manual review

Examples

Example 1: "I have 5,000 contacts with company domains but no emails" --> Set up 6-provider waterfall with domain as primary input. Conditional run: only if email is empty. Estimated cost: 5,000 x avg 6 credits = ~30,000 credits. Expected coverage: 85%+.

Example 2: "My email bounce rate is too high" --> Add MillionVerifier validation column after waterfall. Filter: keep only "valid" results. Use conditional formula to flag "catchall" for manual review. Target: under 2% bounce rate.

Example 3: "Should I run personal email waterfall too?" --> Only if work email waterfall returns empty. Add conditional: "Only run if /work_email is empty". Use separate waterfall with personal email providers. Lower priority than work email.

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

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.

Need help setting it up?

This page tells you what email-waterfall 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.