deepline-quickstart

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

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/deepline-quickstart/SKILL.md

Quality

Content

77%

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

This is a strong, actionable skill with excellent workflow clarity and concrete, executable commands throughout. The fallback chain (Dropleads → Apollo → /deepline-gtm) is well-designed with clear error recovery. Minor weaknesses include some verbosity in the execution flow boilerplate and a structure that may not scale well as more recipes are added.

Suggestions

Consider extracting the 'Execution flow' and 'Session commands reference' sections into a shared reference file if more recipes are added, to avoid repeating the pattern for each recipe.

Tighten the execution flow section — Claude can infer patterns like 'tell the user what you're about to do' from a single concise instruction rather than a numbered sub-list.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and avoids explaining concepts Claude already knows, but there's some redundancy in the execution flow section that repeats general patterns Claude could infer. The recipes themselves are well-structured, though the session commands reference could be tighter.	2 / 3
Actionability	Every step includes fully executable bash commands with complete payloads, specific field names, and concrete parameters. The fallback commands are equally concrete and copy-paste ready, including the Apollo alternative and the last-resort invocation.	3 / 3
Workflow Clarity	The execution flow is clearly sequenced with explicit steps (tell user → register session → run steps with status updates → register output → summarize). Each recipe step has a clear sequence, and there are explicit fallback/error recovery paths (Dropleads fails → try Apollo → last resort /deepline-gtm).	3 / 3
Progressive Disclosure	The content is reasonably well-organized with clear sections and a logical hierarchy, but it's somewhat monolithic for what could grow into multiple recipes. The description mentions 'pick the most relevant recipe below' suggesting multiple recipes were intended, but only Recipe 1 is present. No external file references are used, which is acceptable given the current size but would become problematic as recipes are added.	2 / 3
	Total	10 / 12 Passed

Description

40%

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 too vague to be effective for skill selection. It names the tool (Deepline) and the general intent (demo), but fails to describe what the demo actually does, what concrete actions are performed, or when Claude should select this skill. It needs significantly more specificity and explicit trigger guidance.

Suggestions

Describe the concrete actions the demo performs (e.g., 'Runs a sample Deepline pipeline that processes example data to demonstrate core features like X, Y, Z').

Add an explicit 'Use when...' clause with natural trigger terms such as 'Use when the user asks for a Deepline demo, tutorial, quickstart, example, or wants to see how Deepline works'.

Clarify what 'demo recipe' means — specify the type of recipe, expected output, or workflow so Claude can distinguish this from other Deepline-related skills.

Dimension	Reasoning	Score
Specificity	The description is vague — 'run a quick demo recipe' and 'show how Deepline works' do not describe any concrete actions or capabilities. There is no indication of what the demo actually does.	1 / 3
Completeness	The 'what' is weakly stated (run a demo recipe), and the 'when' is only implied (when the user wants to see how Deepline works). There is no explicit 'Use when...' clause.	2 / 3
Trigger Term Quality	It includes 'Deepline' and 'demo' as trigger terms, which a user might naturally say. However, it lacks variations or additional keywords (e.g., 'tutorial', 'example', 'getting started', 'quickstart') that users might use.	2 / 3
Distinctiveness Conflict Risk	'Deepline demo recipe' is somewhat specific to a particular tool, which reduces conflict risk, but the vague nature of 'demo' could overlap with other tutorial or onboarding skills.	2 / 3
	Total	7 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: getaero-io/gtm-eng-skills
Commit: 449bc08

Reviewed: 1 day 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.