Agent skill · Data & Analytics

lead-enrichment

When the user wants to build data enrichment workflows, score leads against ICP, set up Clay waterfalls, or improve contact data quality. Also use when the user mentions 'enrichment,' 'data enrichment,' 'Clay,' 'waterfall enrichment,' 'ICP scoring,' 'lead scoring,' 'intent data,' 'contact verification,' 'Apollo,' 'ZoomInfo,' or 'data quality.' This skill covers lead enrichment waterfalls, ICP scoring frameworks, and contact verification systems. Do NOT use for technical implementation, code review, or software architecture.

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill lead-enrichment --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 21 KB
Bundled scripts: none
Version: 1.0.0
Path: packages/skills-catalog/skills/(gtm)/lead-enrichment/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill is a framework to build waterfall enrichment systems, ICP scoring frameworks, and contact verification pipelines. It emphasizes sequencing providers to maximize coverage while minimizing cost per verified lead, and to design workflows around Clay (AI enrichment, table-based models) and multiple data providers (Apollo, ZoomInfo, Hunter, FindyMail, Clearbit/Breeze, etc.). It also details a structured ICP scoring approach with three signal layers (Firmographic, Technographic, Intent) and a multi-step enrichment waterfall with defined steps, verification, scoring, and routing. It includes guidance on Clay table structures, credit consumption, and governance rules to manage budget and quality. It explicitly instructs confirming target ICP, stack, data gaps, volume, and budget before starting, and suggests pre-filtering and auditing policies. It covers verification steps (syntax, DNS/MX, SMTP, catch-all, role accounts, confidence scoring) and thresholds for deliverability, plus catch-all handling rules and a comparison of verification tools. It prescribes using a waterfall flow that progresses from pre-qualification to primary, secondary, tertiary providers, then verification, scoring, and routing, with concrete provider roles per use case and sample table column structure. The skill enumerates pricing bands, credits per action, and clay table column usage, ensuring pre-qualification before enrichment and governance on credit usage and re-enrichment.

How it works

  • It prescribes a three-signal ICP scoring model: Firmographic, Technographic, Intent, with an explicit ICP Score formula and weighted components.
  • It defines a multi-step Waterfall Flow: Input Lead -> Pre-qualification -> Step 1 Primary (Apollo/ZoomInfo) -> Step 2 Secondary (Hunter, Dropcontact) -> Step 3 Tertiary (FindyMail, Snov.io) -> Step 4 LinkedIn (Clay AI) -> Verification -> Score + Route.
  • It specifies provider roles by use case (High-volume, Enterprise, Startup) and a provider comparison matrix for coverage and cost.
  • It outlines Clay architecture basics (Table, Enrichment Column, Waterfall Column, AI Column, Formula Column, Integration Push) and a Sample Clay Table Structure with a detailed column order from A to N (and routing in M).
  • It includes Credit Consumption guidelines and Clay pricing plans with credits per action, plus a governance framework (Pre-qualify, Cap per campaign, alerts, audit, re-enrichment).
  • It provides a Contact Verification Pipeline with six checks, confidence thresholds, and catch-all domain handling rules, plus tool comparisons and privacy considerations.

When to use it

Use when the user seeks to build data enrichment workflows, ICP scoring, lead scoring, waterfall enrichment, or contact verification systems. Triggered also by mentions of enrichment, data enrichment, Clay, waterfall enrichment, ICP scoring, lead scoring, intent data, contact verification, Apollo, ZoomInfo, or data quality. Do not use for technical implementation, code review, or software architecture.

What it can touch

The skill references and prescribes workflows using tools and providers: Clay (for table-based enrichment, AI, and workflow routing), Apollo, ZoomInfo, Hunter, FindyMail, Snov.io, Clearbit/Breeze, Dropcontact, Bombora, G2, BuiltWith, Wappalyzer, HG Insights, MillionVerifier, ZeroBounce, NeverBounce. It also mentions Clay as the integration point for AI enrichment and field-level waterfalls, and outlines a Clay table structure with specific column mappings and routing logic.

Caveats

It includes guidance on pricing plans and credits with explicit monthly credit counts and per-action costs, and a governance model that emphasizes pre-qualification and audit cycles. It also provides catch-all handling rules and verification thresholds that imply operational risk if thresholds are not adhered to. It does not provide concrete implementation code or architecture beyond workflow descriptions, and it advises confirming ICP targets, stack, gaps, volume, and budget before starting.

From the SKILL.md

# Lead Enrichment Skill You are a B2B data enrichment architect. You build waterfall enrichment systems, ICP scoring frameworks, and contact verification pipelines that maximize coverage while minimizing cost per verified lead. You know the provider landscape cold and design workflows that sequence providers for maximum incremental yield. ## Before Starting Confirm with the user: (1) target ICP - industry, company size, geography, persona; (2) current stack - CRM, enrichment tools, outreach platforms; (3) data gaps - which fields are missing or unreliable; (4) volume - leads per month; (5) budget - optimizing for coverage or cost. If the user provides a draft workflow or existing Clay table, analyze it before suggesting changes. --- ## Section 1: ICP Scoring Framework ### The Three Signal Layers Every ICP score pulls from three distinct signal categories. Each layer answers a different question about whether to pursue an account. | Signal Layer | What It Tells You | Key Data Points | Primary Tools | |---|---|---|---| | Firmographic | "Does this company match our sweet spot?" | Employee count, ARR, industry, HQ location, funding stage | Clay, Apollo, ZoomInfo, Clearbit | | Technogra

What's inside
Steps it walks through
  1. Before Starting
  2. Section 1: ICP Scoring Framework
  3. The Three Signal Layers
  4. ICP Scoring Formula
  5. Firmographic Fit Scoring (0-100)
  6. Technographic Fit Scoring (0-100)
  7. Intent Score Calculation (0-100)
  8. Composite Score Interpretation
  9. Section 2: Enrichment Waterfall Architecture
  10. What a Waterfall Does
  11. Waterfall Flow
  12. Provider Selection by Use Case
  13. Provider Comparison Matrix
  14. Incremental Coverage by Waterfall Step
Ships with 1 file
  • references/quick-reference.md
More from agent-skills
All skills →
About this skill
What does the lead-enrichment skill do?

When the user wants to build data enrichment workflows, score leads against ICP, set up Clay waterfalls, or improve contact data quality. Also use when the user mentions 'enrichment,' 'data enrichment,' 'Clay,' 'waterfall enrichment,' 'ICP scoring,' 'lead scoring,' 'intent data,' 'contact verification,' 'Apollo,' 'ZoomInfo,' or 'data quality.' This skill covers lead enrichment waterfalls, ICP scoring frameworks, and contact verification systems. Do NOT use for technical implementation, code review, or software architecture.

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill lead-enrichment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going