deepline-monitors

code.deepline.com/deepline-monitors

Deepline Monitors is an access-gated beta feature that provides provider event feeds, including job posts, email replies, funding signals, and buying intent. These event streams flow into your data warehouse and automatically trigger corresponding plays. Only use this skill if you have monitor access. First run `deepline monitors status` to check access; if you do not have access, do not use this skill and inform the user to contact the Deepline team.

Installs · 126View source

Installation

npx skills add https://github.com/code.deepline.com --skill deepline-monitors

Skill files

SKILL.md

Last synced · Aug 29, 2026

skill-metadata.json›

{
  "documents": {
    "SKILL.md": {
      "kind": "entrypoint",
      "title": "Deepline Monitors",
      "tags": [
        "recipe"
      ],
      "providers": []
    }
  }
}

SKILL.md›

---
name: deepline-monitors
description: "ACCESS-GATED beta. Deepline Monitors are provider event feeds (job posts, email replies, funding, intent) that stream into your warehouse and trigger plays. Only use if you have monitor access: run `deepline monitors status` first; if it reports no access, do NOT use this recipe — tell the user to contact the Deepline team."
---

# Deepline Monitors

## Quick Start

```bash
npm install -g deepline
# Fallback for secure sandboxes: mkdir -p "$HOME/.local" && npm config set prefix "$HOME/.local" && export PATH="$HOME/.local/bin:$PATH" && npm install -g deepline --registry https://code.deepline.com/api/v2/npm/
deepline auth register --wait auto
deepline auth wait --timeout 120 # completes Cowork/browser approval; no-op if already connected
deepline auth status
deepline -h
```

This is a recipe shortcut. It pre-selects the deepline-monitors recipe but the **deepline-gtm governs the entire session**.

## Execution order

1. **Invoke `deepline-gtm`** using the Skill tool.
2. **Follow the meta-skill's full routing instructions** - analyze the user's complete prompt and load every sub-doc the meta-skill tells you to. Do not skip docs just because a recipe is pre-selected.
3. **Follow the meta-skill's routing gate for this recipe.** Read the deepline-monitors recipe at `../deepline-gtm/recipes/deepline-monitors.md` (relative to this file) only when that gate routes you to it. Conditional access and safety checks still apply.

The recipe only covers one part of the task. The meta-skill handles everything else the user asked for.