Deepline monitors
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.From its SKILL.md
npx -y skills add getaero-io/gtm-eng-skills --skill deepline-monitorsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 6 commands, including `npm install -g deepline` and 5 more.
SKILL.md
1.6 KB, 299 tokens by cl100k_base, as published. Nobody here has run it
Deepline Monitors
Quick Start
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
- Invoke
deepline-gtmusing the Skill tool. - 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.
- 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.
What ships with it: 1 file
177 B alongside SKILL.md
- skill-metadata.json177 B