Skip to content

ericrisco/rsc-harness / skills/lead-gen

lead-gen

Verified

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).

FileKindSize
SKILL.mdskill md10.4 KB
evals/README.mdmarkdown882 B
evals/cases.yamlconfig2.8 KB
references/data-sources.mdmarkdown4.7 KB
references/scoring-model.mdmarkdown3.5 KB
scripts/verify.shexecutablescript6.3 KB

references/data-sources.md

View on GitHub
# Reference — data sources, the Apollo API flow, and the provenance spec

How to pick providers, run the waterfall, call Apollo's search→enrichment flow, and what every row must carry to stay legal.

## Provider comparison

No single database wins — coverage and accuracy vary by region and segment, which is why waterfall enrichment is the 2025 norm. *(starnus.com / cleanlist.ai / fundraiseinsider.com comparisons, accessed 2026-06-02.)*

| Provider | Coverage | Email accuracy | Best for |
|---|---|---|---|
| Apollo | ~200M contacts | ~78% | Free/credit-free search; broad SMB + mid-market |
| ZoomInfo | 321M+ contacts / 104M+ companies | ~84% | Strongest firmographics; enterprise |
| People Data Labs | Broad person/company graph | Varies | Programmatic fill layer in a waterfall |
| Clay | Orchestrates 100+ sources | Inherits the layer that hit | The waterfall engine itself |

Both Apollo (~78%) and ZoomInfo (~84%) sit at the edge of the high-volume-sender red-flag line, so a verification pass is mandatory regardless of provider.

## Waterfall ordering heuristic

1. Order providers by **accuracy-per-dollar** for your segment (often ZoomInfo for firmographics, Apollo for free volume, PDL/others as fill).
2. Query the cheapest broad layer first (Apollo free search) to get the candidate set.
3. For each row still missing a verified email, query the next layer — **only for the misses**.
4. **Stop at the first verified hit.** You pay once per contact, not once per provider.
5. Drop rows no layer can verify rather than ship them unverified.

Clay can run steps 2–4 for you across 100+ sources; the heuristic is the same whether you orchestrate it by hand or let Clay do it.

## Apollo People Search → Enrichment flow

Search and enrichment are two separate endpoints. Search **does not consume credits** and is capped at **50,000 records per query** (100/page × 500 pages), but returns **no emails or phones**. Contact data comes only from the (credit-consuming) enrichment endpoints. *(docs.apollo.io/reference/people-api-search, accessed 2026-06-02.)*

```http
# Step 1 — search (free, no credits): find people, get IDs + firmographics
POST https://api.apollo.io/api/v1/mixed_people/api_search
Content-Type: application/json
X-Api-Key: <key>

{
  "person_titles": ["VP Engineering", "Head of Data"],
  "person_seniorities": ["vp", "head"],
  "organization_locations": ["United States", "European Union"],
  "organization_num_employees_ranges": ["51,200", "201,500"],
  "currently_using_any_of_technology_uids": ["snowflake", "bigquery"],
  "q_organization_job_titles": ["Data Analyst"],
  "page": 1,
  "per_page": 100
}
# → up to 50,000 records across 500 pages; NO email/phone in the response.
```

```http
# Step 2 — enrich (consumes credits): get email + phone for the chosen IDs
POST https://api.apollo.io/api/v1/people/bulk_match
Content-Type: application/json
X-Api-Key: <key>

{ "details": [ { "id": "<person_id_from_search>" }, ... ],
  "reveal_personal_emails": false }
# → enriches only the rows you pass — dedupe + ICP-filter BEFORE this call so you
#   never spend credits on rows you would have dropped.
```

Available search filters include title, seniority, location, headcount, revenue, 1,500+ technologies, and active job postings — make your ICP technographic/intent criteria map onto these so they are machine-checkable.

## Dedupe against the CRM (before enriching)

Match candidate rows against existing CRM records on **company domain + person email/LinkedIn URL**. Drop:

- Accounts that are already open opportunities (do not cold-touch a live deal).
- Contacts already owned by a rep.
- Current customers, partners, and competitors.

Deduping before enrichment saves credits and prevents the cardinal sin of a rep cold-emailing an active account.

## Provenance / compliance field spec (every row carries this)

A list with no provenance has no defensible lawful basis under GDPR, and purchased/scraped data confers none. *(derrick-app.com / instantly.ai GDPR-B2B guides, accessed 2026-06-02.)* Each row must carry:

| Field | Why it must exist |
|---|---|
| `source` | Provider + acquisition date — the data-source disclosure GDPR requires you surface to the contact |
| `acquired_at` | Date the row was sourced — feeds score decay and freshness checks |
| `verified` | Did the verification pass confirm the email? Unverified rows do not ship |
| `opt_out` | Compliance flag proving the email will carry a one-click opt-out + source disclosure |
| `lawful_basis` | The Art. 6(1)(f) legitimate-interest reference (the LIA exists) for EU contacts |

These collapse into the scored-list CSV's `source` and `opt_out` columns that `scripts/verify.sh` checks; keep the fuller fields in your working file and project the required columns into the handoff CSV.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall