Build a Total Addressable Market list by sourcing accounts and contacts from providers like Apollo, Crustdata, and PDL.

Convert a Clay table configuration into local Deepline scripts. Use when the user provides a Clay table JSON export, a Clay API response (GET /v3/tables/{id} or POST bulk-fetch-records), or a Clay workbook URL and wants to: (1) fetch records using Deepline instead of Clay's API, (2) replicate AI action columns (Claygent, use-ai, chat-gpt-schema-mapper, octave-qualify-person) using deepline enrich with deeplineagent/exa_search/run_javascript, or (3) convert any Clay workflow into a standalone bash+deepline script that runs locally without Clay.

Run a quick Deepline demo recipe to show the user how Deepline works.

Resolve LinkedIn profile URLs from name + company with strict identity validation to avoid false positives.

Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria. Triggers: ICP analysis, niche signals, won vs lost analysis, differential signals, signal discovery, ICP signal report, account scoring signals, lead scoring, first-party signals, buyer signals. Before reading this file, first read gtm-meta-skill to understand the Deepline CLI tool and how to use it. Then read this file for guidance on the task.

Find companies backed by a specific investor or accelerator, then find contacts and build personalized outbound.

Create a cloud Deepline workflow that runs on a recurring cron schedule or via webhook, inspect it, and validate trigger behavior end to end.