CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-monitors

Deepline Monitors are provider event feeds (job posts, email replies, funding, intent) that stream into your warehouse and trigger plays.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/deepline-monitors/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an efficient, well-structured delegation skill: it gives concrete install commands, names the exact skill to invoke, and precisely gates when to read the recipe file. Its only weaknesses are minor — slight repetition of the delegation point and a quick-start command whose purpose is left implicit.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of known concepts, but the closing line 'The recipe only covers one part of the task. The meta-skill handles everything else' and step 2's 'Do not skip docs' both restate the same meta-skill-governs-everything point, so a minor instance could be trimmed.

4 / 5

Actionability

Guidance is concrete and executable — 'npm install -g deepline', 'Invoke `deepline-gtm` using the Skill tool', and an exact relative path '../deepline-gtm/recipes/deepline-monitors.md' — with minor gaps: 'deepline -h' is never connected to the workflow, and execution depends on the external meta-skill's routing.

4 / 5

Workflow Clarity

This is a simple single-purpose delegation skill with an unambiguous, explicitly ordered sequence (invoke the meta-skill, follow its routing, read the recipe only when the gate routes to it), and no destructive or batch operations requiring validation.

5 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and no bundle files of its own; its single reference to the recipe file is one level deep, given as an explicit relative path, and clearly conditionally signaled.

5 / 5

Total

18

/

20

Passed

Description

57%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 clearly identifies a distinctive niche and concrete data types, but it only answers 'what' — there is no guidance on when the skill should be used, and it lacks natural trigger phrases. Adding an explicit 'Use when...' clause would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to set up event monitors for job posts, email replies, funding, or intent signals, or mentions streaming buying signals into their warehouse.'

Include natural synonyms and phrasings users would say, such as 'job postings', 'funding news', 'intent data', or 'sales triggers', to broaden trigger-term coverage.

State the concrete actions the skill performs (e.g. 'set up monitors, stream events into your warehouse, and trigger plays') rather than only describing what the feeds are.

DimensionReasoningScore

Specificity

The description names the domain ('provider event feeds') with concrete specifics — 'job posts, email replies, funding, intent', 'stream into your warehouse', 'trigger plays' — but describes only 1-2 actions rather than a comprehensive list of what the skill does.

3 / 5

Completeness

The 'what' is clearly stated (event feeds streaming into a warehouse that trigger plays), but there is no 'Use when...' clause or any explicit or implicit trigger guidance for when to invoke the skill, which caps completeness at 3.

3 / 5

Trigger Term Quality

Keywords like 'job posts', 'email replies', 'funding', and 'intent' are relevant to the domain, but the description lacks natural trigger phrasing and common variations (e.g. 'job postings', 'intent signals', 'sales triggers') that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

'Deepline Monitors' names a specific niche product with distinct event types (job posts, email replies, funding, intent), making it highly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

14

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.