Skill detail
deepline-gtm
GTM meta skill for prospecting, enrichment, outreach, and lead list building across dozens of data providers, with guides for finding companies and contacts, enriching records, and writing outreach.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: deepline-gtm description: "GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,clay,clickhouse,cloudflare,contactout,contextdev,crustdata-v3,customer_db,databricks,dataforseo,datagma,deepline_ip_to_company,deepline_native,deeplineagent,discolike,dropleads,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,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meta_audiences,millionverifier,nooks,openmart,opensosdata,openwebninja,outreach,parallel,peopledatalabs,podscan,postgres,predictleads,prospeo,quickenrich,rapidapi,redshift,rocketreach,salesforce,salesforge,salesloft,scrapecreators,searchbug,sec_edgar,sentrion,serper,…." --- # GTM Meta Skill ## Quick Start ```bash npm install -g deepline deepline auth register --wait auto deepline -h ``` ## 1. Find the right guidance and capabilities Identify the business outcome, target population, constraints, time horizon, requested destination and spend/authority boundaries. Resolve implementation details yourself: providers, queries, identifier recovery and workflow shape. Ask one concise question with a recommendation only when a missing requirement materially changes the result or external action. Otherwise state a reasonable assumption and proceed. User-specified values override workflow defaults. ### Domain guides Read the relevant guide before new provider work; do not load unrelated guides just to inspect an existing run. | Job | Read and apply | | --- | --- | | Find companies/people, build lead lists, portfolio/VC sourcing, ICP discovery, contact finding or coverage at scale | [Finding companies and contacts](finding-companies-and-contacts.md): filters, provider mix, parallel search, role matching and list-builder delegation. | | Research people/companies; enrich CSVs; find emails, phones or LinkedIn; coalesce, transform, score or add custom signals | [Enriching and researching](enriching-and-researching.md): Play routing, waterfalls, provider evidence and multi-pass research. | | Write cold emails, qualification, personalization, sequences or inspect in Playground | [Writing outreach](writing-outreach.md) and its `prompts.json` templates. Also read enrichment guidance when research informs the writing. Keep outreach context active throughout sequence work. | | Continuous provider event feeds / Monitors | Run `deepline monitors status --json`. Read [Monitors](recipes/deepline-monitors.md) only after exit 0 with `has_access: true`. Exit 1 with `has_access: false` is rollout denial; exit 3 is auth/permission, exit 5 configuration/reachability. Other failures are not denial. | | Public/social source discovery, community language, pre-research source planning or provider coverage/cost comparisons | Use the standalone `deepline-research` skill. | ### Inspect logs or events from existing runs Start with `deepline runs logs --help` for all known kinds and filter examples. A run ID alone reads text logs; omit it or add a search flag to search events. Use `--out` for all retained text, `--kind` for run/step outcomes, and `--payloads` for available details or saved results. Follow `next.logs` to page. These reads execute no providers. Read [Run logs and events](references/run-events.md) for more recipes and SDK fields. ### Discover Plays and tools For new work, look for a suitable prebuilt Play before assembling a custom workflow. Search for the information needed and relevant controls, not only a provider name; describe the selected capability to confirm inputs, outputs and pricing. Names in guides are starting hints, not substitutes for the live contrac