clay-to-deepline

Convert a Clay table configuration into local Deepline scripts. Handles extraction (MCP or script), documentation, action mapping, script generation, and parity validation against Clay ground truth.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/clay-to-deepline/SKILL.md

Quality

Content

72%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 content is a compact, well-structured routing skill that delegates the heavy lifting to deepline-gtm and a single recipe file. Its main gap is the lack of an explicit validation/parity-check feedback loop for what is fundamentally a batch migration operation.

Suggestions

Add a validation checkpoint in the execution order, e.g. a step to run parity validation against Clay ground truth and retry on mismatch, since this is a batch/migration workflow.

Trim the explanatory prose (e.g. 'The recipe only covers one part of the task. The meta-skill handles everything else the user asked for.') to tighten conciseness further.

Surface one or two concrete script-generation or parity-check commands inline so the skill is actionable even before routing to the recipe.

Dimension	Reasoning	Score
Conciseness	The body is lean and largely actionable, with only minor explanatory prose ('This is a recipe shortcut...', 'The recipe only covers one part of the task...') that could be trimmed, fitting the score-4 anchor rather than 5.	4 / 5
Actionability	Provides concrete executable bash commands and a specific recipe path ('../deepline-gtm/recipes/clay-to-deepline.md'), but the actual migration work is delegated to the meta-skill and recipe rather than shown inline, leaving minor gaps.	4 / 5
Workflow Clarity	A clear 3-step sequence is present (invoke deepline-gtm, follow routing, follow the recipe gate), but the skill targets a batch/migration operation with no validation feedback loop in the body, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Under 50 lines, well-organized into Quick Start and Execution order sections, with a single clearly-signaled one-level-deep reference to the recipe file, matching the score-5 anchor for simple skills.	5 / 5
	Total	16 / 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.

The description is specific and distinctive, clearly articulating a multi-step Clay-to-Deepline migration workflow. Its main weakness is the absence of an explicit 'when to use' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when migrating a Clay table to local Deepline scripts or when the user mentions Clay-to-Deepline migration.'

Include a few natural synonyms or variations (e.g. 'Clay table', 'Clay workbook', 'Deepline conversion') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'extraction (MCP or script), documentation, action mapping, script generation, and parity validation' — giving comprehensive coverage of the migration workflow, matching the score-5 anchor.	5 / 5
Completeness	The 'what' is clear but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural domain terms like 'Clay table', 'Deepline scripts', 'extraction', and 'MCP' are present, but synonyms and common variations are missing, fitting the score-4 anchor rather than 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Clay to Deepline migration) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 869569c

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.