CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-engine

Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

60%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 highly actionable with real CLI commands, explicit validation gates, and genuine reference files, but token efficiency is the clear weak point: the pilot/billing policy is repeated across four sections and the publication runbook is inlined where the bundle's own structure shows it belongs in a reference. Consolidating the duplicated policy and splitting the runbook would lift both conciseness and disclosure without losing any guidance.

Suggestions

State the paid-pilot rules (caps, workspace restrictions, aggregate bound, replay accounting) once — either in Workflow step 11 or a dedicated section — and reference that single statement from the Invariants and the publication steps instead of restating it four times.

Move the 11-step "Automatic publication and verification" runbook into a references/ file (parallel to post-fix-verification.md) and keep a short summary plus a link in the body.

Break Workflow step 11's single ~250-word paragraph into sub-bullets (workspace check, record selection, cap setting, disclosure, replay, stop conditions) so each pilot rule is scannable.

DimensionReasoningScore

Conciseness

The paid-pilot/billing-cap/workspace policy is restated four times — Workflow step 11 (a ~250-word run-on paragraph), the final Invariants bullet, the "Automatic publication and verification" intro, and that section's closing bounds paragraph — which is several padded sections rather than the 'some… could be tightened' level of the 3 anchor. It avoids the 1 level only because there is almost no explanation of concepts Claude already knows; the verbosity is repetition, not filler education.

2 / 5

Actionability

Concrete, copy-paste-ready commands appear throughout ("deepline search \"<transition input -> transition outcome>\"", "deepline plays settings set --play <name> --name path --value ...", "deepline run <orchestrator-name> --input '{...}'") along with the Play export signature and a precise deliverables checklist. It falls short of 5 because the orchestrator .play.ts guidance is a shape/signature rather than a worked example, with the full pattern deferred to the reference.

4 / 5

Workflow Clarity

Two dependency-ordered sequences include explicit validation checkpoints ("Validate every edge" enumerating the exact edge cases to test, live-version reconciliation via "deepline plays get", replay verification) and stop-on-failure feedback loops. It misses 5 because the overlapping dual 11-step workflows (Workflow vs. Automatic publication) and the monolithic step 11 blur which sequence governs, leaving minor sequencing ambiguity rather than missing validation.

4 / 5

Progressive Disclosure

Both referenced files (references/state-machine-contract.md, references/post-fix-verification.md) exist and are well-signaled with their purpose, and references are one level deep. It stops at 4 because the body is a full policy manual — the entire "Automatic publication and verification" runbook is inline content of exactly the kind the bundle already demonstrates belongs in references/, alongside post-fix-verification.md.

4 / 5

Total

14

/

20

Passed

Description

83%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 strong description: it names the domain and multiple concrete capabilities in third person, and includes an explicit invocation trigger. The only weakness is narrow trigger coverage — one phrasing ("build an engine") where a couple of natural synonyms would make matching more robust.

DimensionReasoningScore

Specificity

"Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot" lists multiple specific concrete actions (build, publish, verify, run a paid pilot) with a named domain and data plane, matching the comprehensive-coverage anchor; the 4 anchor's 'minor gaps in coverage' does not apply since the skill's actions are fully enumerated.

5 / 5

Completeness

Both halves are explicit: a clear "what" (build/publish/verify a durable state machine over Customer DB tables with a paid pilot) and an explicit "when" ("Invoke this skill explicitly when the user asks to build an engine"). It sits at 4 rather than 5 because the when-clause is a single concrete trigger, while 5-anchor examples supply multiple concrete trigger phrases; it is above 3 because the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

"build an engine", "Deepline Play", "state machine", and "publish" are natural terms a user of this product would say, giving good keyword coverage, but the description relies on a single narrow trigger phrasing and misses variations like "orchestrator" or "create an engine" — fitting the 'a few natural terms missing' anchor rather than the synonym-and-extension coverage of 5.

4 / 5

Distinctiveness Conflict Risk

"Deepline Play", "Customer DB", and "durable state machine" carve out a clear niche with distinct triggers; no other generic skill would match this description, so conflict risk is minimal.

5 / 5

Total

18

/

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