CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-quickstart

Run a quick Deepline demo with a maintained Play.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

93%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 excellent lean skill file: executable commands with concrete examples, honest-reporting guardrails, and a pilot-before-batch pattern for the risky CSV workflow. The only notable gap is that waiting on a terminal run result and recovering from a failed pilot are stated as requirements but not operationalized.

Suggestions

Specify how to check for a terminal run result (e.g. the status/polling command and what terminal states look like) so 'Wait for a terminal run result before exporting' is executable.

Add a short recovery path for a failed or misaligned pilot (inspect the run result, adjust the Play or input, re-run the 4-row pilot) to close the feedback loop.

DimensionReasoningScore

Conciseness

About 50 lean lines that are almost entirely commands; the little prose present carries non-obvious guidance ('Do not use the retired CSV enrichment command or its flags', 'Never substitute a scalar Play for a batch Play unless its contract explicitly accepts rows'). Every token earns its place — anchor 5.

5 / 5

Actionability

Fully executable, copy-paste-ready commands cover both common cases: single-record enrichment with a concrete JSON input example, and a complete CSV pipeline (search, describe, check, 4-row pilot, run, export). Matches anchor 5.

5 / 5

Workflow Clarity

Clear sequences with real checkpoints — credits confirmation before a paid run, a 4-row pilot before the full file, 'Wait for a terminal run result before exporting', and row-alignment review. Falls short of anchor 5 because how to check for a terminal result is unspecified (no status/polling command) and there is no fix-and-retry path if the pilot fails.

4 / 5

Progressive Disclosure

Single-file bundle with no external references needed; ~50 lines organized into clear Quick Start / Single record / CSV sections. Per the rubric's simple-skill guidance, well-organized sections with no need for external files score 5.

5 / 5

Total

19

/

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 is short, accurate, and highly distinctive thanks to the 'Deepline' product name, but it is thin: it names only one action and entirely omits when to use the skill. Adding a 'Use when...' clause and the skill's core capabilities (single-record and CSV enrichment) would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to demo or pilot Deepline enrichment on a record or CSV.'

Name the concrete capabilities in the description: single-record enrichment via Plays and CSV batch enrichment with a pilot run, not just 'Run a quick demo'.

Include natural keywords users would actually say — 'enrich', 'enrichment', 'CSV', 'leads' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Deepline') and one concrete action ('Run a quick demo') with the 'maintained Play' qualifier, but does not list the skill's actual capabilities (single-record enrichment, CSV batch runs). Matches anchor 3: domain plus 1-2 concrete actions, not comprehensive.

3 / 5

Completeness

The 'what' is clear ('Run a quick Deepline demo with a maintained Play') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'Deepline', 'demo', 'quick', and 'Play' are relevant terms, but common user phrasings like 'enrich', 'enrichment', 'CSV', 'batch', or 'leads' are absent. Some relevant keywords with missing variations — anchor 3, not the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

'Deepline' is a unique product name and 'maintained Play' is domain-specific vocabulary, giving a clear niche with minimal risk of triggering for the wrong skill — matches anchor 5.

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