code.deepline.com

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.

All-time #1198 Trending #808 Hot #3807 First seen Jul 7, 2026
8-week activity · all time api

Installation

$ npx skills add https://code.deepline.com

Summary

  • 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.

Also in this package

Other skills from code.deepline.com · top by installs.

npx skills add https://code.deepline.com

Browse all from code.deepline.com

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,588 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14,000 installs

SKILL.md

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

  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.