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

84%

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

86%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.

An exemplary redirect stub: short, fully executable, and unambiguous about its single job of handing off to `deepline-gtm`, with a concrete fallback for locating that skill's entrypoint. The only soft spots are slight redundancy with the frontmatter description and a missing branch when no fallback root exists.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — the fallback path-resolution loop and `deepline plays --help` are pure instructions with no concept explanations. Minor trimmable content remains: the "temporary alias kept so existing prompts, scripts, and saved commands keep working. It will be removed" sentence largely duplicates the frontmatter description, so it sits just below the every-token-earns-its-place 5 anchor.

4 / 5

Actionability

Guidance is fully executable: a copy-paste-ready bash loop that resolves the `deepline-gtm` entrypoint by checking candidate roots in order, a concrete loader invocation, and the specific command `deepline plays --help` covering the common play operations ("write, check, run, publish, or audit").

5 / 5

Workflow Clarity

The sequence is clear: load `deepline-gtm` (loader first, then ordered filesystem fallback with an explicit existence check), follow it for the request, run `deepline plays --help` for play operations, then notify the user once and continue. It stops short of a 5 because there is no branch for the case where none of the candidate roots exist — a minor checkpoint gap rather than absent validation, which keeps it above the level-3 anchor.

4 / 5

Progressive Disclosure

At ~30 lines with no bundle files, the body needs no external references and is well organized into short sections (Quick Start, What to do). Its single reference target (the `deepline-gtm` skill) is one level deep and clearly signaled, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

75%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.

A well-formed deprecation-alias description: it explicitly states what it does and when to use it, with an unambiguous redirect action. Its weaknesses are the thin capability list (a single redirect action) and generic trigger terms (workflow, cron) that create overlap risk with unrelated skills.

Suggestions

Briefly enumerate the concrete capabilities the redirect covers (e.g., creating, checking, running, publishing, and auditing plays via the deepline CLI) so the 'what' is more than a single redirect action.

Drop or narrow the generic triggers 'workflow' and 'cron' (they overlap with unrelated scheduling and workflow skills) and retain the distinctive ones like 'play', 'plays', and '/deepline-plays'.

DimensionReasoningScore

Specificity

The description names the domain ("Deprecated alias. Play work is now part of `deepline-gtm`") and one or two concrete actions ("immediately load and follow the `deepline-gtm` skill instead"), matching the anchor for a named domain with 1-2 concrete actions. It does not list several specific actions, so it falls below the 4 anchor; it is more concrete than the generic, minimal-action 2 anchor.

3 / 5

Completeness

It 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 a concrete trigger phrase, matching the top anchor exactly.

5 / 5

Trigger Term Quality

The trigger list "play, plays, workflow, waterfall, webhook, cron" plus the explicit invocation "/deepline-plays" provides good natural keyword coverage including a plural variation. It misses common synonyms and extensions a 5 would require, but exceeds the 'some relevant keywords, missing variations' level of 3.

4 / 5

Distinctiveness Conflict Risk

"play, plays" are fairly niche, but the generic triggers "workflow", "waterfall", "webhook", and "cron" overlap with unrelated workflow-authoring and scheduling skills, so it could still trigger for the wrong skill. This fits 'somewhat specific but could still overlap with similar skills' rather than the mostly-distinct level 4.

3 / 5

Total

15

/

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