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

77%

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

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and well-structured for a thin routing skill, with executable commands and a single clearly-signaled external reference. The main gap is the absence of an explicit validation checkpoint in the execution-order workflow.

Suggestions

Add a brief verification step in the execution order, e.g. confirm 'deepline auth status' shows connected before invoking deepline-gtm.

Make the routing gate outcome explicit (e.g. 'if the gate does not route to clay-to-deepline, stop and ask') so the delegation has a clear checkpoint.

Consider noting what to do if the recipe file at ../deepline-gtm/recipes/clay-to-deepline.md is missing.

Dimension	Reasoning	Score
Conciseness	The body is lean — a compact Quick Start with executable commands and a short numbered execution order — with no padding or explanations of concepts Claude already knows.	3 / 3
Actionability	Provides copy-paste-ready shell commands (npm install, deepline auth register/wait/status) and concrete routing steps with an explicit recipe file path.	3 / 3
Workflow Clarity	The three execution steps are clearly sequenced, but the workflow is delegation to a meta-skill with no explicit validation/checkpoint for confirming routing or recipe load success.	2 / 3
Progressive Disclosure	Under 50 lines with well-organized sections (Quick Start, Execution order) and a single clearly-signaled one-level-deep reference to the recipe file at a relative path.	3 / 3
	Total	11 / 12 Passed

Description

67%

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, naming concrete migration sub-tasks, but it omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when migrating a Clay table to Deepline scripts or validating Clay→Deepline parity.'

Include natural trigger variations a user might say ('migrate Clay to Deepline', 'convert Clay table', 'Deepline parity check').

Keep the concrete action list as-is — it is already specific and distinct.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'extraction (MCP or script), documentation, action mapping, script generation, and parity validation' — each a specific capability rather than vague language.	3 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' trigger guidance for when to invoke it, capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Uses domain terms a Clay/Deepline user would say ('Clay table configuration', 'Deepline scripts') but lacks common variations and has no natural trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	The Clay→Deepline niche is highly specific and unlikely to overlap with unrelated skills, so it would not trigger for the wrong skill.	3 / 3
	Total	10 / 12 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: 59a5bd2

Reviewed: about 10 hours 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.