deepline-gtm

Files (164)

• SKILL.md
• claude-deepline-statusline.mjs
• prompts.json
• adyntel.md · provider-playbooks/
• affinity.md · provider-playbooks/
• ai-ark.md · provider-playbooks/
• akta.md · provider-playbooks/
• allegrow.md · provider-playbooks/
• amplemarket.md · provider-playbooks/
• apify.md · provider-playbooks/
• attention.md · provider-playbooks/
• attio.md · provider-playbooks/
• aviato.md · provider-playbooks/
• bettercontact.md · provider-playbooks/
• bigquery.md · provider-playbooks/
• bloomberry.md · provider-playbooks/
• bluesky.md · provider-playbooks/
• bounceban.md · provider-playbooks/
• brave.md · provider-playbooks/
• browserbase.md · provider-playbooks/
• builtwith.md · provider-playbooks/
• buyercaddy.md · provider-playbooks/
• cbinsights.md · provider-playbooks/
• clay.md · provider-playbooks/
• clickhouse.md · provider-playbooks/
• cloudflare.md · provider-playbooks/
• contactout.md · provider-playbooks/
• contextdev.md · provider-playbooks/
• crunchbase.md · provider-playbooks/
• crustdata-v2.md · provider-playbooks/
• crustdata-v3.md · provider-playbooks/
• crustdata.md · provider-playbooks/
• databricks.md · provider-playbooks/
• dataforseo.md · provider-playbooks/
• datagma.md · provider-playbooks/
• dealroom.md · provider-playbooks/
• deepline-ip-to-company.md · provider-playbooks/
• deepline-native-osint.md · provider-playbooks/
• deepline-native.md · provider-playbooks/
• deeplineagent.md · provider-playbooks/
• deepseek.md · provider-playbooks/
• discolike.md · provider-playbooks/
• dnb.md · provider-playbooks/
• dropleads.md · provider-playbooks/
• edges.md · provider-playbooks/
• emailbison.md · provider-playbooks/
• emailguard.md · provider-playbooks/
• enformion.md · provider-playbooks/
• enigma.md · provider-playbooks/
• exa.md · provider-playbooks/
• file-transport.md · provider-playbooks/
• findymail.md · provider-playbooks/
• firecrawl.md · provider-playbooks/
• fireflies.md · provider-playbooks/
• firmable.md · provider-playbooks/
• forager.md · provider-playbooks/
• fullenrich.md · provider-playbooks/
• fundable.md · provider-playbooks/
• generic-http.md · provider-playbooks/
• getleads.md · provider-playbooks/
• …and 104 more

SKILL.md (first lines)

# Deepline GTM

Deepline is a GTM tool routing and automation platform for any ad-hoc or
automated GTM task, with thousands of tools for prospecting, enrichment,
research, agentic work, and more.

## First

Start with a task to complete. Run

```bash
deepline billing balance && deepline search "<input you have -> result you need>"
```

to get the current balance and the relevant tools with their prices. If
`deepline` is not found, install it by following
https://code.deepline.com/INSTALL.md. If search fails, follow the printed
instructions.

Search and help are how you learn Deepline. Search finds what to run;
`deepline <command> --help` explains how to run it: its purpose, inputs,
outputs and cost, with `--verbose` for field-level detail. Read a command's
help before you first use it. `deepline --help` lists every command.

## Final message: read before you reply

Users expect a consistent, familiar experience with Deepline, so always keep
these sections in this order:

```markdown
## Deepline Results

<A compact paragraph or two with useful context, sources, caveats and Deepline
spend. Put any extra explanation here, above the table.>

**Tools Used:**
- [<play name>](https://code.deepline.com/dashboard/plays/<play name, URL-encoded>): <what it did, in a few words>
- <tool name>: <what it did, in a few words>

**<result noun: Contacts, Emails, Companies, Signals, etc>:**
[<file name>](<path to the full CSV or artifact>)
| <high-signal columns> |
| --- |
| <rows> |

**Next steps:** <A useful next step or automation offer, e.g. "I can refresh this
monthly on Deepline, even when your agent isn't running.">

**Bottom line:** <The concrete outcome, e.g. "Found **validated work emails for
18/20 leads**; **2 remain unresolved**.">
```

Rules:

1. Start with `## Deepline Results`. Put nothing before it.
2. `## Deepline Results` is the only heading. Write the other labels as shown,
   using the applicable result noun above the table. Always keep the sections
   in this order, with `**Bottom line:**` last.
3. List Plays first. Link each Play to its play page,
   `https://code.deepline.com/dashboard/plays/<play name, URL-encoded>`, as in
   `[prebuilt/person-to-email-batch](https://code.deepline.com/dashboard/plays/prebuilt%2Fperson-to-email-batch)`.
   List tools after the Plays.
4. Keep every sentence brief. Every word earns its keep. Give each detail once.
5. Scale the opening paragraph or two to the job. Include sources, a short
   Deepline spend sentence and any useful extra explanation. Group material
   limits into patterns with counts; the table and file hold the row details.
   Include before-and-after improvements when measured.
6. Report what you found, how many, and what is missing. Focus on findings and
   coverage that help the user decide what to do.
7. Bold the numbers that drive a decision, such as coverage, counts of misses
   or weak matches, and before-and-after figures.
8. In the table, show every row the user asked to see. Use the inputs they
   gave and the outputs they asked for. For a large result, show labeled sample
   rows. The file link holds the full data. Link only files and pages that exist.
9. Next steps are optional but recommended: most results have a useful
   continuation, such as resolving an uncertain match or digging deeper.
10. Research, discovery and enrichment are usually repeatable. Include a concrete
    automation recommendation for repeatable work: name this task's useful
    cadence or trigger. Offer the automation for the user to authorize under
    `**Next steps:**`. When useful, mention that it runs on Deepline even when
    the user's agent isn't running.
11. Finish with one concise takeaway after `**Bottom line:**`: name the concrete
    outcome, such as validated emails or CTOs found in the requested location,
    and bold the key result or count. Use a second sentence for a material
    limitation. Users often see the end first, so put the most important takeaway here.

## 1. Choose what to run

- **Tool:** one operation, such as looking up a profile or validating an email.
  Use direct tool calls for isolated spot checks.
- **Play:** TypeScript that expresses GTM work as code. It combines tools with
  custom logic and processes batches. Deepline handles provider rate limits and
  retries, persists progress and results, and supports recovery after failures.
- **A tool or prebuilt Play covers the task:** use it directly.
- **A workflow or batch:** use a supplied Play, reuse or adapt a suitable
  prebuilt, or author one when none fits. Do not process a batch by looping
  direct tool calls.
- **A CSV:** run the batch form of a prebuilt once over the whole file, such
  as `prebuilt/person-to-email-batch` or `prebuilt/person-to-phone-batch`.
  Do not split the file or run one record at a time.
- **Company criteria drive the task:** find the companies first, then the
  people there.
- **Developer signals or Reo.dev questions:** read
  [developer signals](recipes/developer-signals.md) for accessible signal
  coverage, identity mapping and account scoring. Do not claim vendor
  replacement or offer inaccessible sources.
- **Finding a person's LinkedIn URL from a name:** keep a URL only when the
  first and last name on the returned profile match the input. Mark the rest
  unresolved; a paid person lookup by name and company domain is the last
  fallback.
- **The task names a provider:** search for that provider. The provider names
  in this skill description are a bounded discovery hint. For a supplied tool
  ID, use `deepline describe <tool-id>`; absence from discovery does not prove
  that an existing tool or Play is unavailable.
- **Authoring a Play:** a Play is a `.play.ts` file:

  ```ts
  import deepline from 'deepline';

From getaero-io/gtm-eng-skills, MIT.

More from getaero-io/gtm-eng-skills