CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepline-plays-review

Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a standing rule,” “never regress on this case,” “compare these runs,” “keep improving,” or “add the revised run to the same spreadsheet.” Skip ordinary Play authoring or execution with no human review loop, generic spreadsheet work, and one-off CSV export.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly operational skill body: concrete executable commands with real validation and error-recovery loops, and no filler or explanations of known concepts. The main improvements are tightening repeated breadcrumb/budget guidance and splitting the evaluation-decide methodology into a reference file so the main body stays a lean overview.

Suggestions

Consolidate the breadcrumb and budget/stopping-rule guidance, which currently appears in both 'Establish or resume the loop' and 'Continue, checkpoint, or recover,' into one checklist to save tokens and avoid drift between the two lists.

Move the detailed evaluation methodology (frozen-basis definition, golden dataset column schema, scorecard contents, checkpoint field list) into a references/ file linked one level deep from SKILL.md, keeping the main body as a routing-plus-core-loop overview.

The 'Route expected Workspace failures' error table is valuable but deep in the document; consider placing it near the export/read commands where those failures actually occur, or extracting it alongside the evaluation reference.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of concept explanations Claude already knows, with every section carrying operational guidance. It falls short of the lean-everything-earns-its-place anchor because of repetition: breadcrumbs appear in three places (the 'Establish or resume' checklist, the export section's 'authoritative breadcrumbs,' and the checkpoint list), and budget/stopping-rule guidance is stated both in 'Establish or resume the loop' and again in 'Continue, checkpoint, or recover.'

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: the run receipt pipeline with jq extraction and dataset-identity validation, the export input built with 'jq -n' from guarded env vars, the paginated values/comments reads, and a real helper script (scripts/review-sheet-presentation.mjs, verified present) invoked via 'node "$SKILL_DIR/scripts/review-sheet-presentation.mjs"'. Specific examples cover the common cases (new workbook vs. existing-workbook append, pagination, stale reads).

5 / 5

Workflow Clarity

The loop is stated up front ('revision → run → assess → decide → next revision') and sections sequence it end-to-end with explicit validation checkpoints: pilot on one or two rows before scaling, jq assertions that fail loudly on malformed dataset identity, re-reading fresh Sheet values before decisions, never overwriting a reviewed tab, and an error-routing table with retry/conflict/stale-basis recovery. The destructive/batch cap does not apply because batch export and run operations have explicit verification and feedback loops.

5 / 5

Progressive Disclosure

The body is well-sectioned with a routing table up front and its one bundle file (scripts/review-sheet-presentation.mjs) is real and clearly signaled, with a justified reason for its existence ('never duplicate this layout in a skill script'). It is not a 5 because the single ~275-line monolith inlines the full evaluation methodology (frozen basis, golden dataset schema, scorecard contents, checkpoint fields) that could be split into a one-level-deep reference file, leaving SKILL.md as a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: it states concrete capabilities, gives eight natural trigger phrases, explicitly separates itself from adjacent authoring/spreadsheet skills, and covers both what and when without padding. Every clause is load-bearing and the third-person/imperative trigger form is used correctly.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full review loop — 'review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration' — which is comprehensive coverage for its domain, matching the top anchor rather than the 'several specific actions; minor gaps' anchor at 4.

5 / 5

Completeness

It explicitly answers both 'what' (review a Deepline Play result and hand back feedback, labels, or approval for revision, evaluation, comparison, or bounded iteration) and 'when' (an explicit 'Use this skill when...' clause plus a concrete trigger list and a skip clause), which matches the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Eight natural, quotable trigger phrases ('put this run in a Sheet,' 'review these results,' 'read my feedback,' 'make this a standing rule,' 'never regress on this case,' 'compare these runs,' 'keep improving,' 'add the revised run to the same spreadsheet') comprehensively cover the ways a user would naturally request this skill, including synonym variations. Not 4 because coverage includes variations across review, rule-making, comparison, and iteration intents with no common phrasing missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — the human review loop around Deepline Play results — and actively reduces conflict risk with the skip clause ('Skip ordinary Play authoring or execution with no human review loop, generic spreadsheet work, and one-off CSV export'). Distinct product-specific triggers like 'put this run in a Sheet' and 'add the revised run to the same spreadsheet' keep overlap with generic review or spreadsheet skills minimal.

5 / 5

Total

20

/

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