CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-plays

Deprecated alias. Play work is now part of `deepline-gtm`, and the CLI documents plays itself. Use when a user or script still invokes `/deepline-plays`: immediately load and follow the `deepline-gtm` skill instead. Triggers: play, plays, workflow, waterfall, webhook, cron.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 exemplary redirect stub: it states its purpose in one line, gives fully executable fallback logic for locating the target skill, points to the right CLI help commands, and stays within roughly 25 lines. The only minor trim candidate is the npm-install Quick Start block, which duplicates the target skill's territory.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ("Do not answer from this file; it contains no workflow of its own"), but the Quick Start npm-install block ("npm install -g deepline / deepline -h") is content that belongs in the target skill rather than a redirect stub, a minor instance of over-inclusion matching anchor 4 rather than anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: a complete bash fallback loop ("for candidate in \"$PWD/.skills/deepline-gtm\" ..."), exact CLI pointers ("deepline run --help", "deepline plays --help"), and a specific user-communication instruction ("tell the user once, in a single line"). Matches the anchor 5 example of executable commands covering the common cases.

5 / 5

Workflow Clarity

This is a simple single-purpose skill (redirect to deepline-gtm) whose single action is unambiguous, with an explicit ordered fallback ("trying these roots in order and using the first that exists") and no destructive or batch operations requiring validation. Per the rubric's simple-skill exception, an unambiguous single action scores 5.

5 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections (Quick Start, What to do) and no need for external references — verified that no references/, scripts/, or assets/ bundle files exist. Per the rubric guideline, a short skill with no external-reference needs and good organization scores 5.

5 / 5

Total

19

/

20

Passed

Description

67%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 honest and well-structured for a deprecated alias: it explicitly states what it is, when to use it, and where the real capability now lives, with clear trigger terms. Its weaknesses are inherited from the stub nature — few concrete capabilities of its own and a trigger list mixed with generic high-conflict terms like 'workflow', 'webhook', and 'cron'.

Suggestions

Trim or qualify the generic trigger terms (workflow, webhook, cron) to phrases users would say specifically about plays (e.g., 'run a play', 'deepline play', 'publish a play') to reduce conflict risk with unrelated automation skills.

Add one or two concrete actions the redirected skill covers (e.g., 'create, check, and publish plays') so the description conveys the capability, not just the redirection.

Include natural variations and synonyms of the core terms (plays, waterfall campaign) to improve trigger term coverage from partial to good.

DimensionReasoningScore

Specificity

Names the domain ("Play work is now part of `deepline-gtm`") and one concrete action ("immediately load and follow the `deepline-gtm` skill instead"), which matches the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so it falls short of anchor 4.

3 / 5

Completeness

Explicitly answers both what ("Deprecated alias. Play work is now part of `deepline-gtm`, and the CLI documents plays itself") and when ("Use when a user or script still invokes `/deepline-plays`") with concrete trigger phrases. This clearly matches the anchor 5 example structure rather than the anchor 4 case where 'when' lacks specificity.

5 / 5

Trigger Term Quality

"Triggers: play, plays, workflow, waterfall, webhook, cron" includes some relevant natural terms (play, plays, waterfall) but misses common variations and synonyms (e.g., 'deepline', 'run a play', 'publish'), and several listed terms (workflow, webhook, cron) are generic rather than natural phrases for this niche. Fits anchor 3, not the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

Terms like "play, plays, waterfall" are distinctive to this tool, but "workflow, waterfall, webhook, cron" are broad generic triggers that would overlap with many automation-related skills. Somewhat specific but with real overlap risk, matching anchor 3 rather than the mostly-distinct anchor 4.

3 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

getaero-io/gtm-eng-skills

Path

skills/deepline-plays/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.