ACCESS-GATED beta. Deepline Monitors (dashboard name: Signal Radars) — 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 — every command returns monitor_access_required. Ask a Deepline admin (Admin → Rollouts) for access.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
ACCESS-GATED beta. Deepline Monitors (dashboard name: Signal Radars) — 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 — every command returns monitor_access_required. Ask a Deepline admin (Admin → Rollouts) for access.
This is a recipe shortcut. It pre-selects the deepline-monitors recipe but the deepline-gtm governs the entire session.
Execution order
Invoke deepline-gtm using 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.
