Prospecting
Build a scored B2B prospect list with ICP fit, enrichment sources, and validated emails before outbound.
Overview
Prospecting is an agent skill for the Grow phase that builds ICP-aligned B2B prospect lists with multi-source discovery, qualification, and validated contact data.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill prospectingWhat is this skill?
- Checks product-marketing.md first and branches playbook (e.g. SaaS at defined ACV)
- Phase 1 ICP definition from context or targeted questions (industry, headcount, stack, funding)
- Multi-source discovery: Apollo, Clay, Crunchbase, BuiltWith/Wappalyzer, LinkedIn Sales Nav
- Sources 2–3× target candidates before qualifying; asks what tools you actually have access to
- Non-negotiable email validation (e.g. Truelist) plus scored table and top hot-lead rationales
- Workflow expects sourcing 2–3× the target prospect count before qualifying
- Eval scenario targets 25 prospects with 50–75 candidates sourced first
Adoption & trust: 6.8k installs on skills.sh; 32.4k GitHub stars.
What problem does it solve?
You know who you want to sell to but lack a qualified, verified prospect list tied to real buying signals.
Who is it for?
Indie B2B SaaS or services founders doing first serious outbound with a defined ACV and positioning doc.
Skip if: Pure PLG with no sales motion, or teams that already run a fully instrumented RevOps stack without agent assistance.
When should I use this skill?
You need a B2B prospect list with ICP, multi-source discovery, and validated emails (e.g. RevOps SaaS outbound).
What do I get? / Deliverables
You get a scored prospect table, validated emails, and prioritized hot leads ready for personalized outbound.
- Scored prospect table with signals and email status
- Top 3–5 hot leads with one-sentence rationale each
Recommended Skills
Journey fit
Outbound prospecting and pipeline building sit in the grow phase when you are turning positioning into repeatable sales motion. Lifecycle covers finding, qualifying, and reaching the right buyers—not one-off launch buzz.
How it compares
Structured sales playbook in SKILL.md form—not a one-click data-vendor export or generic lead-gen chat.
Common Questions / FAQ
Who is prospecting for?
Solo and small-team B2B founders and sellers who need ICP-scored lists, enrichment strategy, and email validation before outreach.
When should I use prospecting?
Use it in Grow when you are building pipeline, re-entering outbound after positioning work, or replacing ad-hoc Apollo-only list pulls with a qualified workflow.
Is prospecting safe to install?
Review the Security Audits panel on this Prism page before installing; the skill may reference external sales and enrichment tools you connect separately.
SKILL.md
READMESKILL.md - Prospecting
{ "skill_name": "prospecting", "evals": [ { "id": 1, "prompt": "We're a B2B SaaS selling RevOps tooling at $30K ACV. Build me a list of 25 prospects.", "expected_output": "Should check for product-marketing.md first. Should identify this as the SaaS branch. Should run Phase 1 ICP definition pulling from product-marketing context or asking targeted questions (target industry, headcount range, tech stack signals, funding stage). Should propose discovery sources appropriate for SaaS at $30K ACV: Apollo for breadth, Clay for waterfall enrichment, Crunchbase for funding signals, BuiltWith/Wappalyzer for tech stack, LinkedIn Sales Nav for decision-mapping (manual). Should ask about user's tool access before assuming. Should source 50-75 candidates (2-3x target) before qualifying. Should flag that email validation via Truelist or similar is non-negotiable before final list. Should output SaaS-branch chat table columns (Score | Company | Industry | Size | Signal | Contact | Email status | Confidence) followed by top 3-5 hot leads with one-sentence rationale each. Should reference references/saas-prospecting.md.", "assertions": [ "Checks for product-marketing.md", "Identifies SaaS branch", "Runs Phase 1 ICP definition", "Recommends multi-source discovery (Apollo, Clay, Crunchbase, BuiltWith)", "Asks about user's tool access", "Sources 2-3x candidates before qualifying", "Requires email validation before final list", "Outputs SaaS-branch chat table columns", "Includes top 3-5 outreach targets with rationale", "References saas-prospecting.md" ], "files": [] }, { "id": 2, "prompt": "Find me 25 SaaS companies that just raised a Series B in the last 60 days and use HubSpot.", "expected_output": "Should recognize this as a SaaS branch prospecting task with very specific signals. Should identify the trigger event (Series B in last 60 days) and the technographic filter (uses HubSpot). Should recommend a workflow: (1) Crunchbase or Pitchbook for funding signal filter (Series B + date), (2) BuiltWith or Clay's waterfall for tech stack verification (uses HubSpot), (3) cross-check via business websites and LinkedIn. Should note this is a tight ICP that should yield high-confidence matches if data sources are current. Should flag freshness concerns: Crunchbase data depends on self-reporting, BuiltWith refresh cycles aren't real-time. Should recommend cross-source verification for the funding date specifically. Should output a SaaS-branch chat table with the funding round + date in the Signal column. Should include verified email validation before delivering.", "assertions": [ "Identifies as SaaS branch", "Identifies funding signal + tech stack filter", "Recommends Crunchbase or Pitchbook for funding", "Recommends BuiltWith or Clay for HubSpot verification", "Notes data freshness concerns", "Recommends cross-source verification", "Outputs signal column showing round + date", "Requires email validation" ], "files": [] }, { "id": 3, "prompt": "I run a marketing agency. Find me 25 mid-market manufacturers in the Midwest US who recently hired a new CMO.", "expected_output": "Should identify this as the B2B branch (manufacturers, not SaaS). Should run Phase 1 ICP definition: industry (manufacturing, with NAICS code if precision matters), size (mid-market = typically 200-2000 employees), geography (Midwest US states), trigger event (CMO hire in last 90-180 days). Should propose discovery: Apollo or ZoomInfo for firmographic filter, LinkedIn Sales Nav for CMO hire detection (job changes), Google Alerts on press releases for trigger events. Should warn that CMO hires aren't always in public databases — LinkedIn Sales Nav alerts on job changes is the most reliable source. Should output B2B-branch chat tab