deepline-quickstart

Run a quick Deepline demo recipe to show the user how Deepline works.

Quality

57%

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-quickstart/SKILL.md

Quality

Content

65%

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

The content is highly actionable with copy-paste-ready commands and clear sequencing, but redundancy across the fast path and fallback steps, suppressed validation on a batch operation, and a monolithic structure keep it from the top level on three dimensions.

Suggestions

De-duplicate the repeated dropleads_search_people command by defining the canonical call once and referencing it from Step 1 and the Fallback section.

Add a lightweight final verification checkpoint on the enriched CSV (e.g. confirm at least one email column is populated) even on the fast path, or explicitly justify why verification is intentionally skipped.

Consider moving the detailed fallback steps and CLI-resolution guidance into a referenced file to reduce inline length and improve navigation, since the skill is well over 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is lean and skips concept explanations, but the dropleads_search_people command is repeated across the fast path, Step 1, and the Fallback section, and the enrich command appears twice, so it could be tightened.	2 / 3
Actionability	The fast-path block is fully executable and copy-paste ready with real paths (deepline/data/...), complete JSON payloads, and a working Python normalization script, matching the top anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced with fallback and last-resort error-recovery flows, but the skill explicitly suppresses validation ("Do not ... run extra validation after the enrich command") on a batch enrichment with no final output verification, which the guidelines cap at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but is a single >150-line monolithic file with no bundle references (none exist), and detailed fallback/CLI-resolution content that could be split out is inline, matching the middle anchor.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 concrete and on-brand but minimal: it conveys a single demo action and its purpose without explicit trigger guidance or multiple capability statements. It lands at the middle level on every dimension.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to see Deepline in action, asks for a demo, or wants a quick example of what Deepline can do."

Expand specificity by listing the concrete outcomes the demo produces (e.g. "...finding CTOs with verified emails and LinkedIn profiles") so multiple specific actions are visible.

Broaden trigger terms to cover natural variations like "Deepline demo", "Deepline example", "try Deepline", or "show me Deepline".

Dimension	Reasoning	Score
Specificity	"Run a quick Deepline demo recipe" names a concrete action and domain, but only a single action rather than the multiple specific actions the top anchor requires; it is not vague enough for a 1.	2 / 3
Completeness	It states what the skill does ("Run a quick Deepline demo recipe to show the user how Deepline works") but has no explicit "Use when..." trigger clause, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	"Deepline", "demo recipe", and "show the user how Deepline works" give some natural keywords a user might say, but coverage is thin with no broader use-case variations, matching the middle anchor.	2 / 3
Distinctiveness Conflict Risk	The Deepline brand and quickstart/demo niche make it fairly distinguishable, but it could overlap with sibling Deepline skills (the body references /deepline-gtm), so it is not a clear 3.	2 / 3
	Total	8 / 12 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-quickstart/SKILL.md
Commit: 59a5bd2

Reviewed: about 9 hours 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.