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.

Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal email hashes', 'increase Facebook match rate', 'Google ads audience', 'Meta audience', 'FB audience', or any workflow that turns CRM/customer/contact data into paid ads upload lists. Skip for outbound prospecting sequences, cold email, or pure campaign copywriting.

Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of snowflake_get_semantic_layer / snowflake_run_semantic_query. Skip prospecting, enrichment, contact finding, outbound, or personalization workflows; use deepline-gtm for those.

Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.

Send feedback or bug reports to the Deepline team, including session transcript and environment info.

Create custom Deepline plays/scripts that combine multiple tools and/or other plays, with durable datasets, fallback logic, joins, projections, and custom run/export behavior.

Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a standing rule,” “never regress on this case,” “compare these runs,” “keep improving,” or “add the revised run to the same spreadsheet.” Skip ordinary Play authoring or execution with no human review loop, generic spreadsheet work, and one-off CSV export.

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

Use when discovering niche signals, auditing ICP or won/lost evidence, rescoring accounts, or building account and lead scoring Plays. Triggers on fit scoring, engagement scoring, external proxies, and scoring leakage. Skip pure outreach copy or contributor skill installation tasks.

DRAFT. Use when drafting HubSpot marketing or follow-up emails for GTM events, nurture, or post-event sequences. Templates + structure + anti-slop rules. Not installed by deepline skills.

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

DRAFT. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.

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

Find public community language, market signals, launch feedback, and technical discussion across X/Twitter, Bluesky, Hacker News, and other public social sources.

Read [GUIDE.md](GUIDE.md) for the maintained workflow. Read [README.md](README.md) for setup and tests.

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