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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/deepline-monitors/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clean, well-structured router that delegates detailed work to the deepline-gtm meta-skill and an external recipe file, with concrete install/auth commands and a clear execution order. It is concise and well-organized, with only minor redundancy and the inherent limitation that monitor-specific actions live outside this file.

Dimension	Reasoning	Score
Conciseness	Lean body with no padding of concepts Claude already knows; the brief prose ('This is a recipe shortcut...', 'The recipe only covers one part of the task') slightly restates the execution-order steps, which is minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides concrete, executable commands (npm install, deepline auth register/wait/status) and a specific execution sequence with an explicit recipe path; the monitor-specific actionable steps are delegated to an external recipe file, leaving a minor gap in this body.	4 / 5
Workflow Clarity	Clear three-step 'Execution order' sequence with an auth-status checkpoint in Quick Start; no explicit validate-then-proceed feedback loop, but the skill is a non-destructive router so the destructive-operation cap does not apply.	4 / 5
Progressive Disclosure	Well-organized router skill under 50 lines with a clearly signaled, one-level-deep reference (../deepline-gtm/recipes/deepline-monitors.md) and a tight Quick Start section; the simple-skill exception applies and navigation is easy.	5 / 5
	Total	17 / 20 Passed

Description

65%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is distinctive and names concrete capabilities with natural trigger terms, but it leans heavily on access-gating instructions in second-person voice rather than crisp task-based trigger guidance. Tightening the voice to third person and adding an explicit 'Use when...' task trigger would lift completeness and specificity.

Suggestions

Rewrite in third person to avoid the second-person voice penalty (e.g., 'Streams provider event feeds... Use when the user wants to track job posts, email replies, funding, or intent signals').

Add an explicit task-based 'Use when...' clause so the 'when' is not only an access gate.

Lead with the capability rather than the 'ACCESS-GATED beta' label to keep the trigger terms prominent.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capabilities ('provider event feeds (job posts, email replies, funding, intent) that stream into your warehouse and trigger plays') plus a concrete access-check command, which would rate a 4; reduced by 1 because the description uses second-person voice ('Only use if you have monitor access', 'tell the user'), which the guidelines penalize.	3 / 5
Completeness	Has a clear 'what' (event feeds streaming into warehouse and triggering plays), but the explicit 'when' is purely an access gate ('Only use if you have monitor access: run deepline monitors status first') rather than a task-based trigger, leaving the use-when guidance weakly implied for actual user tasks.	3 / 5
Trigger Term Quality	Good natural keyword coverage with feed-type terms users would actually say ('job posts', 'email replies', 'funding', 'intent') plus 'monitor access', though a few common synonyms or variants are missing.	4 / 5
Distinctiveness Conflict Risk	Clear, narrow niche (Deepline-specific monitor feeds) with distinct access-gated triggers and a unique product name, giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Path: skills/deepline-monitors/SKILL.md
Commit: 3bb8968

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.