Menu

Individual skill

lead-enrichment

Turns a raw or partial prospect list into a send-safe dataset by filling missing fields (work email, direct or mobile phone, title, firmographics, technographics) through a per-field provider waterfall, verifying every email, and stamping freshness. Use when someone says "enrich this list", "find the email for these people", "verify these emails before we send", "what do I do with catch-all domains", "this list is a year old, is it still good", "dedupe and clean this CSV", or "why is my bounce rate spiking". Do NOT use for selecting WHO to target and building the list itself - use prospect-list-builder. Do NOT use for tool-specific credit mechanics and filter syntax - use apollo-prospecting. Pair with cold-email-deliverability for the inbox-protection side of verification.

skills/lead-enrichment/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Lead Enrichment

Enrichment is two jobs that people collapse into one and regret it: **filling** missing fields (a logistics problem - which provider has this contact, at what cost) and **verifying** the ones that touch deliverability (a risk problem - which addresses will bounce or hit a spam trap and torch the sending domain). A list is not "enriched" because the email column is full; it is enriched when every address intended for sending has been independently verified and stamped with a state, and every record carries a freshness date. The costly mistake this skill prevents: treating provider-supplied emails as send-ready. Vendors return pattern-generated guesses (first.last@domain) that were never SMTP-checked - send to those blind and expect a 12-20% bounce rate, which is how domains get throttled or blocklisted.

## Operating procedure

Follow in order: field definition gates the waterfall, the waterfall gates verification, and verification gates everything downstream. Skipping ahead means paying for fields you will not use or sending to addresses you never checked.

### Step 1: gather inputs

Collect before running anything. Label any guessed value as a guess.

- The list: row count, columns present, and source (CRM export, purchase, scrape, conference badge scan). Source predicts quality.
- The downstream play: email sequence, calls, LinkedIn, or multi-channel. This decides which fields are required.