deepline-plays

Create custom Deepline plays/scripts that combine multiple tools and/or other plays, with durable datasets, fallback logic, joins, projections, and custom run/export behavior.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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 tight, actionable routing layer with executable setup commands and a clear execution sequence, but its single external reference points to a file that is not present in the bundle, weakening navigation.

Suggestions

Verify the referenced recipe path '../deepline-gtm/recipes/deepline-plays.md' exists in the deployed bundle, or inline the essential recipe steps so the skill is self-contained.

Consider noting what to do if the deepline-gtm meta-skill or its recipe is unavailable, so the workflow degrades gracefully rather than dead-ending.

Dimension	Reasoning	Score
Conciseness	The body is lean — a short Quick Start of executable commands plus a three-step Execution order — with no padding or explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	It provides copy-paste-ready executable bash commands (npm install, deepline auth register/wait/status) and concrete routing instructions with a real relative path, rather than vague or pseudocode direction.	3 / 3
Workflow Clarity	Execution order is an explicit, ordered three-step sequence (invoke deepline-gtm, follow its routing, additionally read the recipe); for this single-purpose routing skill the sequence is unambiguous, and the destructive/batch feedback-loop requirement does not apply.	3 / 3
Progressive Disclosure	The overview is concise and signals one-level-deep references clearly, but the referenced path '../deepline-gtm/recipes/deepline-plays.md' does not resolve to an existing file, so navigation is not fully achievable.	2 / 3
	Total	11 / 12 Passed

Description

67%

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 specific and distinctive, naming many concrete capabilities tied to a clear Deepline niche, but it lacks any explicit "when to use" trigger guidance and relies on domain jargon over natural user phrasing.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when the user wants to create or compose Deepline plays/scripts that chain tools together.'

Include natural user-facing trigger terms (e.g. 'combine deepline tools', 'chain deepline scripts', 'build a deepline workflow') alongside the technical vocabulary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "combine multiple tools and/or other plays, with durable datasets, fallback logic, joins, projections, and custom run/export behavior" — matching the comprehensive-action anchor rather than the partial score-2 anchor.	3 / 3
Completeness	It clearly answers "what" (the enumerated capabilities) but provides no "Use when..." trigger guidance, so per the guideline a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	The keyword "Deepline plays/scripts" is domain-relevant but the surrounding terms (projections, joins, fallback logic) are internal jargon rather than natural phrases a user would say, and common user variations are missing.	2 / 3
Distinctiveness Conflict Risk	The Deepline-specific framing ("Create custom Deepline plays/scripts") carves a clear niche tied to one tool, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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
Commit: 25492ee

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.