lead-enrichment

tech-leads-club/agent-skills · updated May 23, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/tech-leads-club/agent-skills --skill lead-enrichment
0 commentsdiscussion
summary

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.

skill.md
name
lead-enrichment
description
"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."
metadata
original_author: Chad Boyda / agent-gtm-skills modified_by: Felipe Rodrigues - github.com/felipfr source: https://github.com/chadboyda/agent-gtm-skills version: '1.0.0'

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 LayerWhat It Tells YouKey Data PointsPrimary Tools
Firmographic"Does this company match our sweet spot?"Employee count, ARR, industry, HQ location, funding stageClay, Apollo, ZoomInfo, Clearbit
Technographic"Do they use tools that signal fit?"Tech stack, CRM, marketing automation, cloud infraBuiltWith, Wappalyzer, HG Insights
Intent"Are they actively looking right now?"Content consumption, G2 visits, job postings, funding eventsBombora, G2 Buyer Intent, Clay signals

ICP Scoring Formula

ICP Score = (Firmographic Fit x 0.30) + (Technographic Fit x 0.30) + (Intent Score x 0.40)

Weight intent highest because timing beats targeting. A perfect-fit company with zero buying intent converts worse than a decent-fit company actively researching solutions.

Firmographic Fit Scoring (0-100)

Score each firmographic dimension, then average:

Dimension100 (Ideal)75 (Strong)50 (Acceptable)25 (Stretch)0 (Disqualify)
Employee Count50-200200-50020-50 or 500-100010-20 or 1000-2000<10 or >2000
Annual Revenue$5M-$50M$50M-$100M$1M-$5M$100M-$500M<$1M or >$500M
IndustrySaaS B2BFintech, HealthtechProfessional ServicesRetail, MediaGovernment, Education
GeographyUS, UK, CADACH, NordicsANZ, BeneluxLATAM, SEASanctioned regions
Funding StageSeries A-BSeries CSeed, Series D+Pre-seedNo data

Adjust the ranges to your actual closed-won customer profile. Pull ranges from your CRM data, not assumptions.

Technographic Fit Scoring (0-100)

Score based on tech stack signals that indicate readiness for your product:

Tech_Score = (Stack_Match x 0.50) + (Complexity_Signal x 0.30) + (Migration_Signal x 0.20)

Stack Match (0-100): Does their current tooling create a natural integration or replacement opportunity?

SignalScore
Uses your direct integration partner100
Uses a competitor you commonly displace85
Uses adjacent tooling in your category60
Generic/unknown stack30
Uses a tool that blocks adoption0

Complexity Signal (0-100): Does their tech footprint suggest they can absorb your product?

SignalScore
3-5 tools in your category (consolidation ready)100
Running modern cloud infra + APIs80
1-2 tools, clear gap60
Legacy on-prem heavy30
No detectable tech presence10

Migration Signal (0-100): Are they showing signs of switching?

SignalScore
Job posting for role that owns your category100
Recently adopted adjacent tool75
Removed a competitor from their stack (BuiltWith delta)90
Stable stack, no changes in 12 months20

Intent Score Calculation (0-100)

Intent scoring requires combining multiple signal sources. No single provider captures the full picture.

Intent_Score = max(Bombora_Surge, G2_Intent, First_Party) x 0.60
             + Hiring_Signal x 0.20
             + Funding_Signal x 0.20

Bombora Company Surge scoring:

Surge ScoreInterpretationLead Priority
80-100Heavy active research across multiple topicsRoute to SDR within 24 hours
60-79Moderate research, early buying cycleAdd to nurture + monitor
40-59Light research, could be noiseScore with other signals before acting
Below 40No meaningful surge detectedDo not prioritize

G2 Buyer Intent signals:

Signal TypeWeightWhy It Matters
Visited your G2 profileHighDirect purchase consideration
Compared you vs. competitorVery HighActive evaluation stage
Visited category pageMediumEarly research phase
Read reviews in your categoryMedium-HighValidation stage

First-party intent signals (your own data):

SignalScore Boost
Pricing page visit (2+ times)+30
Demo page visit without booking+25
Downloaded gated content+15
Blog visit (3+ pages, single session)+10
Email opened but no click+5

Composite Score Interpretation

ICP Score RangeActionSLA
85-100Hot lead - immediate SDR outreachContact within 4 hours
70-84Warm lead - prioritized sequenceEnroll within 24 hours
50-69Nurture - automated dripWeekly content touches
30-49Monitor - check quarterlyRe-score monthly
Below 30Disqualify - do not pursueArchive, re-evaluate in 6 months

Section 2: Enrichment Waterfall Architecture

What a Waterfall Does

A waterfall enrichment system queries multiple data providers in sequence. Each provider gets a chance to fill missing fields. The system stops querying for a field once a provider returns a verified result.

Single-provider enrichment typically yields 55-65% coverage. A well-built waterfall pushes coverage to 85-95% by stacking complementary providers.

Waterfall Flow

Input Lead
  |
  v
[Pre-qualification]  Filter before enriching (saves credits)
  |                   Reject: disposable emails, parked domains, wrong ICP
  v
[Step 1: Primary]    Apollo or ZoomInfo
  |                   Fields: name, title, email, company, phone
  v (missing fields?)
[Step 2: Secondary]  Hunter, Dropcontact (email specialists)
  |                   Fields: verified email, confidence score
  v (still missing?)
[Step 3: Tertiary]   FindyMail, Snov.io (deep search + verify)
  |                   Fields: email, phone, LinkedIn URL
  v (still missing?)
[Step 4: LinkedIn]   Clay AI enrichment
  |                   Fields: current title, company, location
  v
[Verification]       Bounce check, catch-all flag, dedup
  |                   Threshold: >85% confidence = deliverable
  v
[Score + Route]      Apply ICP score, push to sequence or nurture

Provider Selection by Use Case

Not every waterfall needs the same providers. Match your stack to your market and budget.

High-volume outbound (1000+ leads/month):

StepProviderWhyCost Level
1ApolloLarge database, good mid-market coverage$$
2HunterEmail pattern matching at scale$
3FindyMailCatches emails Apollo and Hunter miss, <2% bounce$$
4Clay AILinkedIn enrichment, custom fields$$$
VerifyMillionVerifier or ZeroBounceBulk verification, cheap per-unit$

Enterprise targeting (under 500 leads/month):

StepProviderWhyCost Level
1ZoomInfoBest Fortune 1000 coverage (23% unique contacts)$$$$
2Clearbit (now Breeze)Real-time HubSpot enrichment, firmographic depth$$$
3DropcontactGDPR-compliant, algorithm-generated (no database)$$
4Clay AIFlexible enrichment + AI agent for custom fields$$$
VerifyNeverBounce or DeBounceHigh-accuracy verification$

Startup / budget-conscious (under 200 leads/month):

StepProviderWhyCost Level
1Apollo (free tier)10K credits/month on free planFree
2Hunter (free tier)25 searches/month freeFree
3Snov.ioAffordable at $39/month for 1,000 credits$
VerifyMillionVerifier$0.0005/email bulk pricing$

Provider Comparison Matrix

ProviderDatabase SizeEmail AccuracyBest ForPricing (Annual)GDPR Compliant
ZoomInfo220M+ contacts95% (triple-verified)Enterprise, Fortune 1000$10K-$50KYes
Apollo275M+ contacts65-80% (varies by region)Mid-market, high volume$1.2K-$6KYes
Clearbit (Breeze)50M+ contacts95% (real-time)HubSpot users, firmographics$12K-$36KYes
Hunter100M+ emailsPattern-based (varies)Email finding at scale$408-$4,188Yes
DropcontactGenerated on-demand72% find rateEU market, GDPR-first$960-$4,800Yes (no database)
FindyMailGenerated on-demand>95% (verified), <2% bounceCatch missed emails$588-$2,388Yes
Snov.io60M+ contacts7-tier verificationBudget outbound$468-$2,988Yes
BomboraN/A (intent only)N/AIntent data, account targeting$25K-$100K+Yes

Incremental Coverage by Waterfall Step

Typical coverage gains when adding each provider in sequence:

Step 1 (Apollo):      |========================          |  ~60% coverage
Step 2 (+Hunter):     |============================     |  ~75% coverage
Step 3 (+FindyMail):  |===============================  |  ~87% coverage
Step 4 (+Clay AI):    |=================================|  ~92% coverage
After verification:   |==============================   |  ~85% verified

The drop after verification is expected. Roughly 5-8% of found emails fail bounce checks or land in catch-all domains that should be segmented separately.


Section 3: Clay Workflow Design

Clay Architecture Basics

Clay operates on a table-based model. Each row is a lead. Each column is a data field. Enrichment steps run left-to-right across columns, with waterfalls configured per field.

Core Clay concepts:

ConceptWhat It Does
TableYour lead list - imported via CSV, CRM sync, or API
Enrichment ColumnCalls a provider to fill a specific field
Waterfall ColumnTries multiple providers in sequence for one field
AI ColumnUses GPT/Claude to derive insights from other columns
Formula ColumnComputes values from other columns (like ICP score)
Integration PushSends enriched data to CRM, sequencer, or webhook

Credit Consumption Guide

Clay charges credits per enrichment action. Budget carefully.

Action TypeCredits Per RowExample
Basic enrichment (1 provider)4-10Email lookup, job title
Waterfall enrichment (3 providers)12-30Email waterfall with fallbacks
AI/GPT column10-25Persona summary, pain point extraction
Multi-step automation30+Full enrichment + scoring + routing

Credit math: 1,000 leads at 25 credits/lead = 25,000 credits. Starter plan handles that in 12.5 months, Explorer in 2.5 months, Pro in 0.5 months. Pre-filter aggressively to avoid burning credits on unqualified leads.

Clay Pricing (2026)

PlanPrice/MoCredits/MoPer Credit
Free$0100N/A
Starter$1492,000$0.075
Explorer$34910,000$0.035
Pro$80050,000$0.016
EnterpriseCustomCustomCustom

Sample Clay Table Structure

Build your enrichment workflow in this column order:

Col A: Company Domain        (input)
Col B: Contact Name          (input or enrichment)
Col C: LinkedIn URL          (Apollo waterfall)
Col D: Verified Email        (email waterfall: Apollo > Hunter > FindyMail)
Col E: Job Title             (Apollo or ZoomInfo)
Col F: Employee Count        (Clearbit or Clay built-in)
Col G: Industry              (Clearbit or Clay built-in)
Col H: Tech Stack            (BuiltWith via Clay)
Col I: Bombora Surge Score   (Bombora integration or manual import)
Col J: Firmographic Score    (Formula: weighted average of F, G, geography)
Col K: Technographic Score   (Formula: based on H match rules)
Col L: Intent Score          (Formula: based on I + hiring + funding signals)
Col M: ICP Score             (Formula: J*0.30 + K*0.30 + L*0.40)
Col N: AI Personalization    (AI column: generate first-line based on B, E, H)
Col O: Routing               (Formula: if M > 85 then "hot" elif M > 70 then "warm")

Credit Governance Rules

  1. Pre-qualify before enriching - domain check + firmographic filter before spending on email waterfall
  2. Cap per campaign - no single campaign burns more than 40% of monthly credits
  3. Alert at 75% - Slack/email alert when usage crosses 75% of monthly allowance
  4. Audit weekly - credits spent vs. leads enriched vs. leads qualified (target >60% qualification)
  5. 90-day re-enrichment - re-enrich stale contacts before including in new campaigns

Section 4: Contact Verification Pipeline

Unverified cold email lists carry 10-30% invalid addresses. Sending to bad addresses destroys sender reputation within a few campaigns. Google, Yahoo, and Microsoft now enforce bounce rates under 2% and spam complaints under 0.3%.

Verification Pipeline Steps

StepCheckActionCost
1Syntax validationRemove malformed addresses (missing @, double dots)Free
2DNS/MX lookupVerify domain has valid mail serverFree
3SMTP verificationConfirm mailbox exists at providerProvider-based
4Catch-all detectionFlag domains that accept all addressesProvider-based
5Role account checkFlag info@, support@, admin@, sales@Provider-based
6Confidence scoringAssign final deliverability scoreComputed

Confidence Score Thresholds

ConfidenceClassificationAction
>0.85DeliverableSafe to send. Include in sequences.
0.70-0.85RiskySend in small batches. Monitor bounce rate per batch.
0.50-0.69Catch-all/UnverifiableSegment separately. Maximum 50 per day. Watch closely.
<0.50Invalid/High RiskReject. Do not send. Re-enrich with alternate provider.

Catch-All Domain Handling

Catch-all domains accept every email sent to them, even addresses that do not exist. They create silent deliverability decay because campaigns appear sent but never reach decision-makers.

Rules for catch-all addresses:

  • Never mix catch-all addresses into your primary sending pool
  • Send catch-all segments from a separate sending domain
  • Limit to 20-50 catch-all sends per domain per day
  • Track reply rates separately; if reply rate drops below 1%, stop sending to that domain
  • Re-verify catch-all addresses every 30 days

Verification Tool Comparison

ToolVerification MethodCatch-All DetectionBulk SpeedPricing
MillionVerifierSMTP + proprietaryYes1M/hour$0.0005/email
ZeroBounceSMTP + AI scoringYes100K/hour$0.008/email
NeverBounceSMTP + real-time APIYes50K/hour$0.008/email
DeBounceSMTP + disposable detectYes500K/hour$0.001/email
BouncerSMTP + toxicity checkYes200K/hour$0.005/email

Deliverability Protection Checklist

Before sending any enriched list to outreach:

  • All emails verified within the last 7 days
  • Bounce rate on verification under 2%
  • Catch-all addresses segmented into separate pool
  • Role accounts (info@, support@) removed or deprioritized
  • Sending domain has SPF, DKIM, and DMARC configured
  • Sending domain warmed for at least 14 days
  • Daily send volume does not exceed 50 per inbox per day (cold)
  • Spam complaint rate on prior campaigns under 0.3%

Section 5: Performance Benchmarks

Expected Conversion Lift from Enrichment

MetricBefore WaterfallAfter WaterfallImprovement
Email coverage rate55-65%85-95%+30-40%
Email bounce rate7-15%<2% (verified)-70-85%
Connect rate (cold call)4-6%8-12%+80-100%
Pipeline generatedBaseline+37%Significant
Meeting-to-customer conversionBaseline+27%Significant
MQL-to-SQL rate (with intent)8-12%15-25%+80-100%

Cost-Per-Verified-Lead Benchmarks

ApproachCost Per LeadCoverageQuality
Single provider (Apollo)$0.05-$0.1560%Medium
Two-step waterfall$0.15-$0.3578%Medium-High
Three-step waterfall$0.30-$0.6088%High
Full waterfall + verification$0.50-$1.0092% verifiedVery High
Full waterfall + intent scoring$1.50-$3.0092% + scoredPremium

ROI Calculation Framework

Cost:  Clay Pro ($800) + Apollo ($99) + FindyMail ($49) + MillionVerifier ($25) = $973/mo
Yield: 2,000 enriched > 1,840 verified (92%) > 1,012 ICP-qualified (55%)
       > 30 meetings (3%) > 12 opps (40%) > 3 closed-won (25%) at $15K ACV = $45K/mo
ROI:   $45,000 / $973 = 46x

Adjust conversion rates for your actual pipeline. The framework matters more than the sample numbers.


Section 6: Compliance

Compliance by Region

RequirementUS (CAN-SPAM/CCPA)EU (GDPR)UK (UK GDPR)
B2B email consentOpt-out modelLegitimate interestLegitimate interest
Data source docsRecommendedRequiredRequired
Right to erasureCCPA: YesRequiredRequired
Data retentionDisclosure requiredDefine and enforceDefine and enforce

Provider Notes

  • Dropcontact generates contacts algorithmically without a database (GDPR-native)
  • Apollo, ZoomInfo, Clearbit are compliant as platforms; you own your usage basis
  • Clay is compliant, but third-party providers accessed through Clay may not be. Verify each.
  • Bombora cooperative data is compliant; downstream outreach must follow local regulations

Safe Enrichment Practices

  1. Document your legal basis (legitimate interest for B2B is standard)
  2. Track which provider sourced each contact
  3. Honor opt-out and erasure requests within 30 days
  4. Do not enrich or contact individuals who have previously opted out
  5. Review provider DPAs annually

Examples

  • User says: "Set up lead enrichment for our outbound" → Result: Agent asks budget and volume; recommends waterfall tier (e.g. Clay + Apollo for $200–1K/mo); outlines steps: import → pre-filter → waterfall → verify (confidence >0.85) → score → route to SDR/sequence; suggests CRM push and 90-day re-enrich.
  • User says: "Our email bounce rate is high" → Result: Agent checks verification (MillionVerifier, NeverBounce) and confidence threshold; recommends catch-all segment and list hygiene; suggests <2% bounce target and re-verification before each campaign.
  • User says: "Which enrichment tools should we use?" → Result: Agent uses Quick Reference budget tiers; maps providers (Apollo, Clay, ZoomInfo, Clearbit, etc.); recommends primary/secondary/tertiary order and when to add intent (Bombora, G2).

Troubleshooting

  • Low email coverage after waterfallCause: Weak providers or wrong order. Fix: Put best provider first; add LinkedIn/FindyMail as fallback; target >85% coverage; track per-provider fill rate.
  • ICP score not predicting meetingsCause: Wrong weights or stale data. Fix: Recalibrate firmographic/technographic/behavioral weights; ensure intent signals fresh; A/B test score bands (e.g. >85 hot, 70–84 warm).
  • Credits burning too fastCause: Enriching everyone or wrong filters. Fix: Pre-filter by domain, industry, geo; set confidence threshold (e.g. 0.85 outreach, 0.50 nurture); cap credits per qualified lead (<50).

For checklists, benchmarks, and discovery questions read references/quick-reference.md when you need detailed reference.


Related Skills

  • positioning-icp - Define the ICP that enrichment scores against. Start here if ICP is undefined.
  • ai-cold-outreach - Use enriched data in personalized cold email sequences. Enrichment feeds outreach.
  • ai-sdr - Automate SDR workflows that consume enriched, scored leads.
  • gtm-engineering - Build the technical infrastructure (APIs, webhooks, CRM integrations) that connects enrichment to the rest of the stack.
  • solo-founder-gtm - Budget-optimized enrichment for founders doing their own outbound.
how to use lead-enrichment

How to use lead-enrichment on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add lead-enrichment
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/tech-leads-club/agent-skills --skill lead-enrichment

The skills CLI fetches lead-enrichment from GitHub repository tech-leads-club/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/lead-enrichment

Reload or restart Cursor to activate lead-enrichment. Access the skill through slash commands (e.g., /lead-enrichment) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.856 reviews
  • Pratham Ware· Dec 28, 2024

    lead-enrichment fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Evelyn Garcia· Dec 28, 2024

    I recommend lead-enrichment for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aanya Okafor· Dec 28, 2024

    lead-enrichment is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ama Perez· Dec 12, 2024

    Solid pick for teams standardizing on skills: lead-enrichment is focused, and the summary matches what you get after install.

  • Valentina Tandon· Nov 19, 2024

    Solid pick for teams standardizing on skills: lead-enrichment is focused, and the summary matches what you get after install.

  • Yusuf Huang· Nov 19, 2024

    lead-enrichment reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Nia Garcia· Nov 3, 2024

    I recommend lead-enrichment for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Nia Johnson· Oct 22, 2024

    Useful defaults in lead-enrichment — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Evelyn Sethi· Oct 10, 2024

    lead-enrichment has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Zara Singh· Oct 10, 2024

    Registry listing for lead-enrichment matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 56

1 / 6