Skip to content

getaero-io/gtm-eng-skills / skills/deepline-gtm

deepline-gtm

Unverified

GTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,buyercaddy,cbinsights,clay,clickhouse,close,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,deepseek,discolike,dnb,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,kickbox,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meerapi,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,particle,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,….

FileKindSize
SKILL.mdskill md15.9 KB
claude-deepline-statusline.mjsexecutablescript25.0 KB
prompts.jsonconfig297.9 KB
provider-playbooks/adyntel.mdmarkdown1.2 KB
provider-playbooks/affinity.mdmarkdown825 B
provider-playbooks/ai-ark.mdmarkdown10.6 KB
provider-playbooks/akta.mdmarkdown1.5 KB
provider-playbooks/allegrow.mdmarkdown4.6 KB
provider-playbooks/amplemarket.mdmarkdown2.8 KB
provider-playbooks/apify.mdmarkdown1.8 KB
provider-playbooks/attention.mdmarkdown449 B
provider-playbooks/attio.mdmarkdown5.6 KB
provider-playbooks/aviato.mdmarkdown756 B
provider-playbooks/bettercontact.mdmarkdown1.7 KB
provider-playbooks/bigquery.mdmarkdown1019 B
provider-playbooks/bloomberry.mdmarkdown935 B
provider-playbooks/bluesky.mdmarkdown139 B
provider-playbooks/bounceban.mdmarkdown1.6 KB
provider-playbooks/brave.mdmarkdown422 B
provider-playbooks/browserbase.mdmarkdown1.0 KB
provider-playbooks/builtwith.mdmarkdown1.0 KB
provider-playbooks/buyercaddy.mdmarkdown2.3 KB
provider-playbooks/cbinsights.mdmarkdown436 B
provider-playbooks/clay.mdmarkdown875 B
provider-playbooks/clickhouse.mdmarkdown1.1 KB
provider-playbooks/close.mdmarkdown2.6 KB
provider-playbooks/cloudflare.mdmarkdown2.3 KB
provider-playbooks/contactout.mdmarkdown8.3 KB
provider-playbooks/contextdev.mdmarkdown582 B
provider-playbooks/crunchbase.mdmarkdown742 B
provider-playbooks/crustdata-v2.mdmarkdown490 B
provider-playbooks/crustdata-v3.mdmarkdown8.4 KB
provider-playbooks/crustdata.mdmarkdown6.8 KB
provider-playbooks/databricks.mdmarkdown3.5 KB
provider-playbooks/dataforseo.mdmarkdown950 B
provider-playbooks/datagma.mdmarkdown6.0 KB
provider-playbooks/dealroom.mdmarkdown632 B
provider-playbooks/deepline-ip-to-company.mdmarkdown480 B
provider-playbooks/deepline-native-osint.mdmarkdown1.5 KB
provider-playbooks/deepline-native.mdmarkdown25.1 KB
provider-playbooks/deeplineagent.mdmarkdown2.7 KB
provider-playbooks/deepseek.mdmarkdown1.2 KB
provider-playbooks/discolike.mdmarkdown6.2 KB
provider-playbooks/dnb.mdmarkdown1.4 KB
provider-playbooks/dropleads.mdmarkdown10.2 KB
provider-playbooks/edges.mdmarkdown875 B
provider-playbooks/emailbison.mdmarkdown634 B
provider-playbooks/emailguard.mdmarkdown243 B
provider-playbooks/enformion.mdmarkdown9.3 KB
provider-playbooks/enigma.mdmarkdown1.7 KB
provider-playbooks/exa.mdmarkdown1.4 KB
provider-playbooks/file-transport.mdmarkdown739 B
provider-playbooks/findymail.mdmarkdown880 B
provider-playbooks/firecrawl.mdmarkdown2.4 KB
provider-playbooks/fireflies.mdmarkdown988 B
provider-playbooks/firmable.mdmarkdown1.3 KB
provider-playbooks/forager.mdmarkdown2.3 KB
provider-playbooks/fullenrich.mdmarkdown2.1 KB
provider-playbooks/fundable.mdmarkdown2.0 KB
provider-playbooks/generic-http.mdmarkdown348 B
provider-playbooks/getleads.mdmarkdown2.2 KB
provider-playbooks/gong.mdmarkdown488 B
provider-playbooks/google-ads-audiences.mdmarkdown2.0 KB
provider-playbooks/google-calendar-availability.mdmarkdown1.6 KB
provider-playbooks/google-calendar.mdmarkdown1.1 KB
provider-playbooks/google-sheets.mdmarkdown842 B
provider-playbooks/google-workspace.mdmarkdown2.1 KB
provider-playbooks/govfiles.mdmarkdown1.8 KB
provider-playbooks/grain.mdmarkdown1.0 KB
provider-playbooks/hackernews.mdmarkdown208 B
provider-playbooks/harvestapi.mdmarkdown3.5 KB
provider-playbooks/heyreach.mdmarkdown1.6 KB
provider-playbooks/hubspot.mdmarkdown3.3 KB
provider-playbooks/hunter.mdmarkdown849 B
provider-playbooks/icypeas.mdmarkdown1.8 KB
provider-playbooks/instantly.mdmarkdown1.6 KB
provider-playbooks/integration-operation.mdmarkdown704 B
provider-playbooks/intercom.mdmarkdown275 B
provider-playbooks/ipqs.mdmarkdown1.7 KB
provider-playbooks/kaspr.mdmarkdown822 B
provider-playbooks/kernel.mdmarkdown875 B
provider-playbooks/leadmagic.mdmarkdown5.3 KB
provider-playbooks/lemlist.mdmarkdown7.5 KB
provider-playbooks/limadata.mdmarkdown636 B
provider-playbooks/linkedin-ads-audiences.mdmarkdown629 B
provider-playbooks/luma.mdmarkdown3.2 KB
provider-playbooks/lusha.mdmarkdown3.5 KB
provider-playbooks/meerapi.mdmarkdown1.2 KB
provider-playbooks/meta-audiences.mdmarkdown4.8 KB
provider-playbooks/millionverifier.mdmarkdown618 B
provider-playbooks/nooks.mdmarkdown1.0 KB
provider-playbooks/notion.mdmarkdown724 B
provider-playbooks/openmart.mdmarkdown2.3 KB
provider-playbooks/opensosdata.mdmarkdown4.0 KB
provider-playbooks/openwebninja.mdmarkdown315 B
provider-playbooks/outreach.mdmarkdown2.6 KB
provider-playbooks/parallel.mdmarkdown4.4 KB
provider-playbooks/particle.mdmarkdown2.0 KB
provider-playbooks/peopledatalabs.mdmarkdown4.5 KB
provider-playbooks/pipedrive.mdmarkdown582 B
provider-playbooks/pitchbook.mdmarkdown606 B
provider-playbooks/podscan.mdmarkdown2.7 KB
provider-playbooks/polymarket.mdmarkdown2.2 KB
provider-playbooks/postgres.mdmarkdown553 B
provider-playbooks/predictleads.mdmarkdown622 B
provider-playbooks/prospeo.mdmarkdown2.4 KB
provider-playbooks/quickenrich.mdmarkdown595 B
provider-playbooks/rapidapi.mdmarkdown2.5 KB
provider-playbooks/rb2b.mdmarkdown247 B
provider-playbooks/redshift.mdmarkdown763 B
provider-playbooks/reo-write.mdmarkdown1.6 KB
provider-playbooks/reo.mdmarkdown2.0 KB
provider-playbooks/resend.mdmarkdown3.6 KB
provider-playbooks/salesforce.mdmarkdown3.6 KB
provider-playbooks/salesforge.mdmarkdown274 B
provider-playbooks/salesloft.mdmarkdown1.0 KB
provider-playbooks/scrapecreators.mdmarkdown3.4 KB
provider-playbooks/searchbug.mdmarkdown637 B
provider-playbooks/sec-edgar.mdmarkdown1.6 KB
provider-playbooks/sentrion.mdmarkdown737 B
provider-playbooks/serper.mdmarkdown1011 B
provider-playbooks/slack.mdmarkdown21.1 KB
provider-playbooks/smartleads.mdmarkdown11.8 KB
provider-playbooks/snitcher.mdmarkdown302 B
provider-playbooks/snowflake.mdmarkdown768 B
provider-playbooks/socrata.mdmarkdown3.2 KB
provider-playbooks/sumble.mdmarkdown1.3 KB
provider-playbooks/tamradar.mdmarkdown1.4 KB
provider-playbooks/test-unhinted.mdmarkdown505 B
provider-playbooks/test.mdmarkdown254 B
provider-playbooks/theirstack.mdmarkdown4.4 KB
provider-playbooks/theswarm.mdmarkdown1.4 KB
provider-playbooks/treg.mdmarkdown1.5 KB
provider-playbooks/trestle.mdmarkdown3.7 KB
provider-playbooks/trykitt.mdmarkdown862 B
provider-playbooks/twitterapi.mdmarkdown3.6 KB
provider-playbooks/unipile.mdmarkdown4.8 KB
provider-playbooks/upcell.mdmarkdown715 B
provider-playbooks/vector.mdmarkdown257 B
provider-playbooks/versium.mdmarkdown690 B
provider-playbooks/wiza.mdmarkdown2.0 KB
provider-playbooks/wizleads.mdmarkdown1.1 KB
provider-playbooks/zerobounce.mdmarkdown1.3 KB
provider-playbooks/zoho-crm.mdmarkdown630 B
provider-playbooks/zoominfo.mdmarkdown1.2 KB
recipes/account-orgchart.mdmarkdown35.6 KB
recipes/build-tam.mdmarkdown3.7 KB
recipes/clay-to-deepline.mdmarkdown26.8 KB
recipes/deepline-monitors.mdmarkdown32.5 KB
recipes/developer-signals.mdmarkdown14.7 KB
recipes/find-qualified-titles.mdmarkdown5.2 KB
recipes/portfolio-prospecting.mdmarkdown3.6 KB
recipes/small-business-prospecting.mdmarkdown3.0 KB
references/clay-action-mappings.mdmarkdown40.0 KB
references/clay-api-surface.mdmarkdown18.6 KB
references/clay-extraction.mdmarkdown16.2 KB
references/industry-radars.mdmarkdown3.3 KB
references/monitor-contract-reference.mdmarkdown25.9 KB
references/monitor-operations.mdmarkdown12.4 KB
references/monitor-sdk.mdmarkdown3.2 KB
references/run-events.mdmarkdown14.3 KB
scripts/clay-extract-bookmarklet.jsscript10.5 KB
scripts/clay-extract-bookmarklet.url.txtmarkdown8.2 KB
scripts/clay-extract.pyscript17.9 KB
scripts/clay-har-miner.pyscript5.8 KB
scripts/clay-to-deepline.mjsscript134.1 KB
scripts/contact-accuracy-audit.pyscript8.9 KB
scripts/fixtures_contact_accuracy_audit.jsonconfig5.5 KB
scripts/fixtures_current_role.jsonconfig10.3 KB
scripts/flatten-search-contact-persons.pyscript3.3 KB
scripts/select-current-role.pyscript12.2 KB
scripts/validate-emails.pyexecutablescript2.0 KB
skill-metadata.jsonconfig2.2 KB
writing-outreach.mdmarkdown14.1 KB

provider-playbooks/dropleads.md

View on GitHub
<!-- skill-tool-compat: dropleads_email_verifier -- Existing exact-ID calls and Plays remain supported during the documented discovery outage; this guide does not select it for new workflows. -->

<!-- skill-tool-compat: dropleads_mobile_finder -- Existing exact-ID calls and Plays remain supported during the documented discovery outage; this guide does not select it for new workflows. -->

<!-- skill-tool-compat: dropleads_email_finder -- Existing exact-ID calls and Plays remain supported during the documented discovery outage; this guide does not select it for new workflows. -->

<!-- skill-tool-compat: dropleads_search_people -- Existing exact-ID calls and Plays remain supported during the documented discovery outage; this guide does not select it for new workflows. -->

<!-- skill-tool-compat: dropleads_get_lead_count -- Existing exact-ID calls and Plays remain supported during the documented discovery outage; this guide does not select it for new workflows. -->

# Dropleads Playbook

Dropleads is hidden from tool discovery because of upstream reliability issues. Choose another provider for new workflows. Exact calls and existing Plays remain supported; the guidance below applies to those existing integrations.

Use Dropleads as a two-phase flow: low-cost contact discovery first, paid enrichment second. Do not use Dropleads people search as the first step for account discovery.

## 1) Start with low-cost discovery

- Use `dropleads_get_lead_count` to size the audience before any paid call.
- Use `dropleads_search_people` to inspect masked contacts and validate ICP filters (free).
- Use `dropleads_search_people` after you already have target account domains, by passing `filters.companyDomains`. It is a contact search primitive, not a dependable way to discover target accounts.
- Do not build joins or account-discovery flows that depend on every returned lead having `companyDomain`. Treat returned `companyDomain` as optional; if you need account domains as the source of truth, use a company-native search/enrichment tool first.
- Tighten filters until sample rows clearly match role, industry, and geo expectations.
- Key filter fields: `filters.jobTitles`, `filters.seniority` (VP/Director/Manager/Senior/Entry/Intern), `filters.industries`, `filters.departments`, `filters.companyDomains`, `filters.employeeRanges`, `filters.personalCountries`, `filters.personalStates`, `filters.personalCities`, `filters.organizationCountries`, `filters.organizationStates`, `filters.organizationCities`, `pagination.page`, `pagination.limit`. Use `personal*` for the contact's location and `organization*` for company HQ; a person's location is not necessarily their employer's HQ. Use title terms like `CEO`, `CTO`, or `Founder` for C-level searches; do not pass `C-Level` as a Dropleads seniority value — Dropleads' own API docs list it, but live validation rejects it. `filters.seniorityExclude` and `filters.departmentsExclude` take the same exact values as their include twins.

### Filter best practices

All Dropleads filters nest under the `filters` object. Pagination nests under `pagination`. The canonical payload shape:

```json
{
  "filters": {
    "companyDomains": ["microsoft.com"],
    "jobTitles": ["CTO", "VP Engineering"],
    "seniority": ["VP", "Director"],
    "personalCountries": { "include": ["United States"] }
  },
  "pagination": { "page": 1, "limit": 25 }
}
```

**Quick reference — correct filter keys:**

| Filter      | Correct key                                                                                 | Why                                                                                                                                                                                                                                                          |
| ----------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Company     | `filters.companyDomains`                                                                    | Exact domain match for known accounts. Prefer this when you already have domains; do not rely on people-search results to discover a complete account-domain list. `companyNames` does fuzzy substring matching — "Microsoft" pulls in unrelated businesses. |
| Person geo  | `filters.personalCountries`, `filters.personalStates`, `filters.personalCities`             | Filters the contact's location. Each field uses an `{ "include": [...], "exclude": [...] }` object.                                                                                                                                                          |
| Company geo | `filters.organizationCountries`, `filters.organizationStates`, `filters.organizationCities` | Filters the company HQ, not the contact's location. Each field uses an `{ "include": [...], "exclude": [...] }` object.                                                                                                                                      |
| Seniority   | `filters.seniority`, `filters.seniorityExclude`                                             | Exact values only: `VP`, `Director`, `Manager`, `Senior`, `Entry`, `Intern`. Use `jobTitles` terms like `CEO`, `CTO`, or `Founder` for C-level searches.                                                                                                     |
| Department  | `filters.departments`, `filters.departmentsExclude`                                         | Exact values only: `Engineering`, `Sales`, `Marketing`, `Operations`, `Finance`, `HR`, `Product`, `Customer Success`, `Legal`, `IT`.                                                                                                                         |
| Industry    | `filters.industries`                                                                        | Exact strings from Dropleads. Pilot with a broad search first when unsure.                                                                                                                                                                                   |

### Exclude filters use the same vocabulary as their include twin

`seniorityExclude` and `departmentsExclude` take the exact same values as `seniority` and `departments`. Prime-DB itself silently ignores an unrecognized value in either exclude list: the exclusion you asked for never happens, the call still returns 200, and the result set still shifts because the filter key is present. Deepline rejects unknown values with a 422 instead of letting a wrong answer look like a valid one.

Also note that sending `seniorityExclude` at all drops leads that carry no seniority in Prime-DB, so it narrows results beyond the levels you name. On a `sephora.com` sample: 1514 leads with no seniority filter, 1058 with all six levels included, 94 with all six excluded.

### Geo filters are best-effort, not verified

Dropleads geo filters (`personalCountries` / `personalStates` / `personalCities` and `organizationCountries` / `organizationStates` / `organizationCities`) match against **self-reported, LinkedIn-sourced location text** — they are not verified against the contact's actual location. Treat them accordingly:

- **City-level is the loosest match and leaks.** `personalCities` can return contacts whose stated city loosely matches even when their real location differs, and non-US contacts can appear under a US-city filter (e.g. a Bulgarian contact surfacing under `personalCities: San Francisco` + `personalCountries: United States`). Country/state are more reliable.
- **Person vs. company location are different fields.** `personal*` filters the contact's own location; `organization*` filters the company HQ. Don't conflate them — filtering a remote employee by company HQ city (or vice versa) drops or leaks legitimate matches.
- **Verify geo when precision matters.** Combine `personalCountries`/`personalStates` with `personalCities`, then post-filter the returned leads on their `country`/`state`/`city` (and exclude obvious mismatches) before trusting the result or spending on enrichment. Do not assume the filter alone guarantees the geo.

## 2) Escalate paid calls only for shortlisted targets

- Run `dropleads_email_finder` for contacts that passed the discovery pass.
- Run `dropleads_mobile_finder` only when phone is required for the workflow.
- For larger or uncertain authorized enrichment, use a small representative pilot and check quality before scaling. Do not add a pilot run or repeat approval for a small supplied Play; inspect its existing results without paid repair.

## 3) Gate outbound with verifier status

- Treat `invalid`, `catch_all`, and `unknown` as non-send by default.
- Treat `valid` as the only status that passes automatic send gates.
- Respect `credits_charged` in responses for post-execution billing accuracy.

## 4) Practical sequencing

1. Count segment (`dropleads_get_lead_count`).
2. Sample segment (`dropleads_search_people`).
3. Pre-score titles with local JavaScript if looking for a specific profile (e.g. founders, GTM engineers).
4. Validate work history and signals against data from an authorized source or a user-provided export.
5. Extract signals with local JavaScript from that data (e.g. founder detection, hiring signals).
6. Enrich emails via waterfall (`dropleads_email_finder` first, then other providers).
7. Verify candidate emails (`dropleads_email_verifier` or `leadmagic_email_validation`).
8. For larger or uncertain work, expand within the authorized scope after the sample quality is confirmed. This sequence is planning guidance, not a requirement to run extra discovery or enrichment when inspecting a supplied Play or its results.

## 5) Account discovery boundary

For account-based pipelines, start with a company-native source that returns account domains as first-class results. Feed those domains into Dropleads via `filters.companyDomains` to find contacts at known accounts. Dropleads may include `companyDomain` on returned people, but it is not guaranteed enough to be the join key that creates the account universe.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall