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.From its SKILL.md
npx -y skills add getaero-io/gtm-eng-skills --skill clay-to-deeplineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- runs commandsInstructs the agent to run 6 commands, including `npm install -g deepline` and 5 more.
- fetches URLsInstructs the agent to fetch 1 URL, including https://code.deepline.com/api/v2/npm/.
SKILL.md
1.4 KB, 303 tokens by cl100k_base, as published. Nobody here has run it
Clay → Deepline Migration
Quick Start
npm install -g deepline
# Fallback for secure sandboxes: mkdir -p "$HOME/.local" && npm config set prefix "$HOME/.local" && export PATH="$HOME/.local/bin:$PATH" && npm install -g deepline --registry https://code.deepline.com/api/v2/npm/
deepline auth register --wait auto
deepline auth wait --timeout 120 # completes Cowork/browser approval; no-op if already connected
deepline auth status
deepline -h
This is a recipe shortcut. It pre-selects the clay-to-deepline recipe but the deepline-gtm governs the entire session.
Execution order
- Invoke
deepline-gtmusing the Skill tool. - Follow the meta-skill's full routing instructions - analyze the user's complete prompt and load every sub-doc the meta-skill tells you to. Do not skip docs just because a recipe is pre-selected.
- Follow the meta-skill's routing gate for this recipe. Read the clay-to-deepline recipe at
../deepline-gtm/recipes/clay-to-deepline.md(relative to this file) only when that gate routes you to it. Conditional access and safety checks still apply.
The recipe only covers one part of the task. The meta-skill handles everything else the user asked for.
What ships with it: 1 file
187 B alongside SKILL.md
- skill-metadata.json187 B