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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 with a clean one-level reference to the recipe, but it lacks an explicit validation/checkpoint step for the migration result, leaving workflow clarity just below the top anchor.

Suggestions

Add an explicit validation checkpoint after the recipe runs (e.g., run parity validation against the Clay table and only declare success when outputs match ground truth).

State what to do on validation failure (fix and re-run) to close the feedback loop for the migration workflow.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no over-explanation of concepts Claude knows; every line ('This is a recipe shortcut...', 'The recipe only covers one part...') earns its place by steering behavior, matching the top anchor.	3 / 3
Actionability	Provides fully executable commands (npm install, deepline auth register/wait/status) and a concrete file path with a specific tool invocation, copy-paste ready per the top anchor.	3 / 3
Workflow Clarity	Execution order is clearly sequenced (1-3) and includes an auth status check, but there is no explicit validation checkpoint on the migration outcome itself — it is implicitly delegated to the recipe, fitting the middle anchor.	2 / 3
Progressive Disclosure	Clear overview with a well-signaled one-level-deep reference to '../deepline-gtm/recipes/clay-to-deepline.md'; no nested references and no bundle files present, so content is appropriately split per the top anchor.	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 clearly scoped to a distinct niche, but it omits explicit 'when to use' trigger guidance and relies on somewhat jargon-heavy terms, capping completeness and trigger term quality.

Suggestions

Add a 'Use when...' clause naming natural user phrases (e.g., 'Use when migrating a Clay table to Deepline, converting Clay enrichment actions to scripts, or replicating Clay workflows locally').

Soften jargon like 'parity validation against Clay ground truth' with a more user-natural phrasing such as 'verify output matches the original Clay table'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'extraction (MCP or script), documentation, action mapping, script generation, and parity validation against Clay ground truth' — matching the top anchor.	3 / 3
Completeness	Clearly answers 'what' but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant domain terms ('Clay table', 'Deepline scripts', 'extraction', 'MCP', 'script') but leans on jargon like 'parity validation' and lacks common user-facing variations, sitting between anchors 2 and 3.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche — converting Clay table configs to Deepline scripts — with distinct triggers unlikely to fire for unrelated skills.	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
Commit: 25492ee

Reviewed: 1 day 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.