CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-triage

Diagnose failing, stuck, partial, or incorrect Deepline Plays, including when no Play is named. Use deepline-gtm for the primitives, reproduce safely, propose an evidence-backed fix, and apply it after approval. For customer troubleshooting; skip platform incident response.

Quality

85%

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

81%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 a tightly written, well-sequenced debugging methodology: five phases each carry specific evidence-gathering directives, safety constraints, and validation checkpoints, with an explicit error-recovery loop. It is instruction-only (commands delegated to deepline-gtm), which it handles well, though a few convoluted sentences and unshown artifacts like the handoff format keep conciseness and actionability at 4.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific directives and assumes competence (never explains what Deepline or a Play is), matching the level-4 anchor of efficient prose with minor trim opportunities. It is not level 5 because a few sentences are convoluted and could be tightened (e.g., 'load each skill once rather than restarting when their routing links meet', 'A later successful run or an empty historical export alone cannot establish what happened to them'); it is not level 3 because there is no padded or unnecessary explanation of known concepts.

4 / 5

Actionability

Concrete, specific guidance throughout — 'Read the causal error behind the final failure message. Trace the affected row back through its logs, retained tool response, input, and pinned source revision; compare with a working run' — with commands appropriately delegated to deepline-gtm, matching the level-4 anchor of mostly executable guidance with minor gaps. It is not level 5 because some artifacts are described but never shown (e.g., the 'paste-ready handoff' has no format or example); it is not level 3 because the steps specify exact evidence to examine, conditions to check, and approval gates rather than high-level hints.

4 / 5

Workflow Clarity

A clearly sequenced five-phase workflow (find → trace → reproduce → propose → apply/verify) with explicit validation checkpoints ('show the expected case failing before the change and passing after the smallest fix', 'Verify the repaired revision and the original failing case') and a feedback loop on failure ('If verification fails, revisit the cause instead of stacking speculative fixes or expanding retries and spend'), matching the level-5 anchor. Approval is required before destructive or live operations, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

Well-organized single-file structure — a Quick Start overview followed by five clearly headed phases — with all content appropriately inline for a process skill and no bundle files to misplace, matching the level-4 anchor of good structure with minor organization gaps. It is not level 5 because there are no well-signaled reference files (the under-50-line exception does not apply to this ~85-line body), and the 'deepline-gtm' delegation, while clearly signposted, is to a separate skill rather than a navigable reference; it is not level 3 because nothing that belongs in a separate file is inlined and navigation via headers is easy.

4 / 5

Total

17

/

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.

The description is strong: it names the domain, enumerates concrete actions across the full diagnose-to-apply lifecycle, and explicitly bounds scope against the sibling deepline-gtm skill and platform incident response. The only soft spot is the 'when' clause, which conveys audience and exclusions rather than concrete user trigger phrases, keeping completeness and trigger coverage at 4.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Diagnose failing, stuck, partial, or incorrect Deepline Plays', 'reproduce safely', 'propose an evidence-backed fix', 'apply it after approval' — covering the full triage lifecycle, plus the edge case 'including when no Play is named'. This matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage); it is not level 4 because there are no meaningful coverage gaps in the action set.

5 / 5

Completeness

The 'what' is explicit (diagnose, reproduce, propose, apply fixes to Plays) and a 'when' exists via 'For customer troubleshooting; skip platform incident response', matching the level-4 anchor where both are present but 'when' could be more explicit. It is not level 5 because it lacks a concrete 'Use when a customer reports...' trigger phrase; it is not level 3 because the audience/scope clause plus the named failure states give real, explicit trigger guidance rather than a merely implied 'when'.

4 / 5

Trigger Term Quality

Natural terms users would say are present — 'failing', 'stuck', 'partial', 'incorrect', 'troubleshooting' — matching the level-4 anchor of good coverage with a few natural terms missing. It is not level 5 because common synonyms like 'broken', 'error', or 'not working' are absent, and not level 3 because multiple natural failure-state phrases are covered, not just one domain keyword.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — failing 'Deepline Plays' triage — and explicitly disambiguates from the closest conflicting skill ('Use deepline-gtm for the primitives', 'skip platform incident response'), matching the level-5 anchor of a clear niche with distinct triggers and minimal conflict risk.

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