Deepline Gtm
Route CSV-heavy prospecting, enrichment, scoring, and outbound activation through Deepline with provider playbooks instead of ad-hoc API spaghetti.
Overview
Deepline GTM is an agent skill most often used in Grow (also Validate research and Launch distribution) that routes prospecting, enrichment, scoring, and outbound activation through Deepline and linked provider playbooks
Install
npx skills add https://github.com/code.deepline.com --skill deepline-gtmWhat is this skill?
- Meta router for Deepline GTM: prospect, enrich, qualify, score, personalize, activate
- Dozens of named providers (Apollo, Hunter, Instantly, HubSpot, Salesforce, Snowflake, etc.) via playbooks
- CSV-heavy workflows with safety gates and quality defaults before execution
- Sub-docs for command chains; provider-specific steps live in provider-playbooks
- Description enumerates 50+ named GTM and data providers routed through playbooks
- Governance split: meta skill for routing and safety gates; execution detail in sub-docs and provider-playbooks
Adoption & trust: 3.7k installs on skills.sh.
What problem does it solve?
You have lead CSVs and a stack of enrichment and sequencer tools but no consistent routing, safety checks, or provider defaults before spend hits APIs.
Who is it for?
Founders running outbound with Deepline, waterfall enrichment, and multi-provider stacks (Apollo, Instantly, HubSpot, etc.).
Skip if: Builders with no outbound motion, no CSV or CRM workflow, or who only need generic copywriting without data providers.
When should I use this skill?
User mentions Deepline, CSV processing, lead or account research, waterfall enrichment, email or LinkedIn lookup, personalization, scoring, or campaign activation.
What do I get? / Deliverables
The agent picks Deepline GTM paths, applies governance defaults, and hands off to the right sub-docs and provider playbooks for execution.
- Routed GTM execution plan with provider playbook references
- Qualified, enriched list ready for sequencer or CRM activation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Grow lifecycle is the canonical shelf because the skill governs lead qualification, personalization, and campaign activation after you have something to sell. Lifecycle fits outbound sequences, enrichment waterfalls, and CRM or sequencer handoffs rather than one-time idea research.
Where it fits
Build LinkedIn or Meta audience exports after scoring and verification gates pass.
Activate Smartlead or Lemlist sequences with personalized fields from waterfall enrichment.
Sync enriched account facts to Snowflake or HubSpot for funnel reporting.
How it compares
GTM orchestration meta-skill with provider playbooks—not a single static integration skill for one API.
Common Questions / FAQ
Who is deepline-gtm for?
Solo builders and small teams doing B2B outbound, list building, and sequencer or CRM activation with Deepline and many data vendors.
When should I use deepline-gtm?
In Grow when activating campaigns and lifecycle outbound; in Validate when researching accounts from a CSV; in Launch when pushing audiences to ads or distribution channels; whenever the user names Deepline, enrichment, or CSV processing.
Is deepline-gtm safe to install?
It implies network calls, third-party data providers, and often CRM or ad platform access—review the Security Audits panel on this Prism page before connecting production keys.
SKILL.md
READMESKILL.md - Deepline Gtm
# GTM Meta Skill Use this skill for prospecting, account research, contact enrichment, verification, lead scoring, personalization, and campaign activation. ## 1) What this skill governs - Route GTM decisions, safety gates, and provider/quality defaults before execution. - Keep long command chains and tooling nuance in sub-docs; provider-specific implementation detail in `provider-playbooks/*.md`. - Provide clear entry points for both paid and non-paid workflows, including `--rows 0:1` one-row pilots. ## Process/goal Customer is generally trying to go from "I have an ICP" to "Here's a list of prospects with email/linkedin and very personalized content or signals". They may be anywhere in this process, but guide them along. **Discovery order: companies first, then people.** When the task requires finding contacts at companies matching criteria (portfolio, ICP, hiring signal), discover the company set first, then find people at each company. Do not start with broad people-search queries. ### Documentation hierarchy - Level 1 (`SKILL.md`): decision model, guardrails, approval gates, links to sub-docs. - Level 2 (phase docs): [finding-companies-and-contacts.md](finding-companies-and-contacts.md), [enriching-and-researching.md](enriching-and-researching.md), [writing-outreach.md](writing-outreach.md), `prompts.json`. - Level 2.5 (`recipes/*.md`): step-by-step playbooks for specific tasks (email lookup, LinkedIn resolution, waterfall patterns, contact finding, actor contracts). Search like code with Grep. - Level 3 (`provider-playbooks/*.md`): provider-specific quirks, cost/quality notes, and fallback behavior. No-loss rule: moved guidance remains fully documented at its canonical level and is linked from here. ## 2) Read behavior — MANDATORY before any execution **STOP. Do not call any provider, run any `deepline tools execute`, or write any search command until you have opened the correct sub-doc for your task.** These skill docs and sub-docs are not generic documentation — they are distilled from hundreds of real runs and encode exactly what works, what fails, and why. They contain validated parameter schemas, correct filter syntax, parallel execution patterns, tested sample payloads, and known pitfalls that took many iterations to discover. Think of them as shortcuts: reading a doc for 5 seconds saves you from 10 failed tool calls, wasted credits, and garbage output. Every time an agent skips reading the docs and tries to "figure it out" from first principles, it re-discovers the same failure modes that are already documented and solved. SKILL.md is the routing layer — it tells you WHERE to go, not HOW to execute. The sub-docs and task-specific skills contain the HOW. Without them you will guess parameters, pick wrong providers, run searches sequentially instead of in parallel, and produce garbage results. This has happened repeatedly. ### Open the right doc BEFORE executing **This i