Deepline Monitors

SkillCommunication

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.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Deepline Monitors skill

What this skill tells your AI

The instructions your AI receives, as published by getaero-io/gtm-eng-skills in skills/deepline-monitors/SKILL.md and read by ahel’s review.

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

  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.

Signals

GitHub stars
58
Forks
11
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
deepline-monitors
Source
github.com/getaero-io/gtm-eng-skills