CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clay-to-deepline

Move Clay tables, workflows, functions and Signals to Deepline Plays and Monitors, and compare what the same run costs in Clay and in Deepline. Use for any Clay migration, Clay export or bookmarklet JSON, Clay CLI workspace, "convert this Clay table", Clay credit cost, or "is Deepline cheaper than Clay". Reads a Clay CLI export or a bookmarklet / clay-extract.py JSON file. Makes the Plays, proves formula parity on real rows, and prices both sides.

Quality

91%

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

78%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 lean, well-structured launcher that defers to a governing meta-skill, with concrete commands and an unambiguous routing sequence. Its weaknesses are minor: the delegation point is repeated three times, and all actual migration mechanics live outside this file, so standalone actionability and validation are limited.

Suggestions

State the meta-skill-governs-everything point once (e.g., in the Execution order intro) and cut the repetitions in the Quick Start note and closing line.

Add one validation checkpoint after step 3, e.g., confirm the recipe's parity check ran on real rows before reporting pricing, so the workflow has an explicit feedback step.

Include a one-line example of the actual invocation outcome (e.g., the deepline command that makes the Plays) so the body is actionable even before the recipe is loaded.

DimensionReasoningScore

Conciseness

The ~24-line body is lean with no explanations of concepts Claude already knows, but the governance point ("the deepline-gtm governs the entire session") is made three times — in the Quick Start note, step 2 ("Do not skip docs just because a recipe is pre-selected"), and the closing line ("The meta-skill handles everything else the user asked for"). This is the anchor-4 pattern of efficient content with minor repetition that could be trimmed, not the every-token-earns-its-place level 5.

4 / 5

Actionability

It gives concrete executable commands ("npm install -g deepline", "deepline -h"), a specific tool invocation ("Invoke `deepline-gtm` using the Skill tool"), and an exact relative path for the recipe. However, the actual migration mechanics promised by the description (making Plays, proving formula parity, pricing) are entirely delegated to out-of-file content, leaving minor gaps — matching anchor 4 rather than the fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

The execution order is a clearly sequenced 1-2-3 list, and step 3's routing gate ("only when that gate routes you to it. Conditional access and safety checks still apply") acts as an explicit conditional checkpoint. It falls short of anchor 5 because there are no validation or feedback steps for the work itself (e.g., confirming the recipe loaded or the parity check succeeded), though no destructive operations are performed directly in this file.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized Quick Start and Execution order sections, and a single clearly-signaled, one-level-deep reference ("Read the clay-to-deepline recipe at `../deepline-gtm/recipes/clay-to-deepline.md` (relative to this file)") with an explicit path annotation. No bundle files exist in this skill, and nothing that belongs elsewhere is inlined — matching the simple-skill exception for a 5.

5 / 5

Total

17

/

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.

The description is exemplary: concrete actions, explicit 'Use for' triggers with quoted natural user phrases, and a clearly distinct two-product niche with minimal conflict risk. It is dense but every phrase does work — no filler or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "Move Clay tables, workflows, functions and Signals to Deepline Plays and Monitors", "compare what the same run costs", "proves formula parity on real rows", "prices both sides" — plus concrete input formats ("Clay CLI export or a bookmarklet / clay-extract.py JSON file"). This matches the anchor for comprehensive coverage of specific actions; a 4 would require minor gaps in coverage, but migration, cost comparison, input parsing, and parity verification are all named.

5 / 5

Completeness

It explicitly answers both questions: the "what" is moving Clay artifacts to Deepline Plays/Monitors and pricing both sides, and the "when" is an explicit "Use for any Clay migration, Clay export or bookmarklet JSON..." clause with concrete trigger phrases. This is the anchor-5 pattern (both what and when with concrete triggers); a 4 would require the 'when' to be less explicit, but it lists six distinct triggers.

5 / 5

Trigger Term Quality

It includes natural phrases users would actually say — "convert this Clay table", "is Deepline cheaper than Clay", "Clay credit cost" — plus synonyms (Clay migration, Clay export, bookmarklet JSON, Clay CLI workspace) and specific tool/file names (clay-extract.py). This is comprehensive natural-term coverage including quoted user phrasings; a 4 would mean a few natural terms are missing, which is not the case.

5 / 5

Distinctiveness Conflict Risk

It names both products explicitly (Clay, Deepline) and targets a clear niche — Clay-to-Deepline migration and cost comparison — with triggers like "is Deepline cheaper than Clay" that would not fire for any other skill. A 4 would imply minor overlap risk with closely related skills, but no other plausible skill matches these triggers.

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/clay-to-deepline/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.