Individual skill
lead-gen
Use when building and qualifying a prospect list before anyone reaches out — a falsifiable ICP, named accounts/contacts from Apollo/ZoomInfo/Clay, deduped against the CRM, tiered by fit+intent+engagement. NOT writing or sending the outreach (that is cold-outreach), NOT tracking the deal after first contact (that is sales-pipeline).
skills/lead-gen/SKILL.md
Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 10, 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)
- 578
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- cline Repository topic
- codex Repository topic
- coding-assistant Repository topic
- cursor Repository topic
- lead-generation Declared skill tag
- prospecting Declared skill tag
- icp Declared skill tag
- lead-scoring Declared skill tag
- sales Declared skill tag
- sales Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,697 bytesSKILL.mdcore · 10,697 bytesSKILL.mdcore · 10,697 bytesSKILL.mdcore · 10,697 bytesSKILL.mdcore · 10,697 bytesevals/README.mddoc · 882 bytesevals/cases.yamlasset · 2,914 bytesreferences/data-sources.mddoc · 4,827 bytesreferences/scoring-model.mddoc · 3,614 bytesscripts/verify.shruns · 6,459 bytes
Read excerpt
# Lead Gen — The List and the Model That Ranks It
*You turn "we sell X to Y" into a deduplicated, scored, compliance-cleared roster of named accounts and people. You define the target, you build the list, you rank it — then you stop. What you produce is a prioritized roster plus the rationale that ranked it; the hand-off is the finish line, not the campaign.*
## The pipeline — three phases, two gates
Run these in order. Each gate is a hard stop: do not advance until the prior phase produced its artifact.
1. **Define the target** → a falsifiable ICP + persona. *Why: you cannot dedupe or score against a vibe; a vague ICP guarantees reps chase the wrong companies.*
2. **Build the list** → sourced, deduped, verified rows with provenance. *Why: an unverified or undocumented list is a deliverability and legal liability before a single email goes out.*
3. **Score & prioritize** → tiered list (A/B/C) with subscores + handoff packet. *Why: an unsorted list means reps work the easy-to-reach names, not the right ones.*
Between phase 2 and the handoff sits the **compliance gate** (GDPR LIA + CAN-SPAM). Run it *before* you hand anything off, never after the first send.