
Clay To Deepline
- 18.6k installs
- code.deepline.com
clay-to-deepline is a Deepline recipe that converts Clay table configurations into local Deepline scripts with parity validation against Clay outputs.
About
clay-to-deepline is a Deepline GTM recipe shortcut for converting Clay table setups into local Deepline automation scripts. It handles extraction via MCP or scripts, documentation, action mapping, script generation, and parity validation against Clay ground truth outputs. Agents must invoke deepline-gtm first, obey the meta-skill routing for the entire user prompt, then read ../deepline-gtm/recipes/clay-to-deepline.md for the migration workflow. The recipe covers only the Clay-to-Deepline slice while the meta-skill loads any additional docs the session requires. Developers use it when moving enrichment workflows off Clay while preserving behavioral parity with existing table logic.
- Migrates Clay tables to Deepline scripts with extraction, mapping, generation, and parity checks.
- Supports extraction through MCP or scripted paths plus action mapping documentation.
- Requires deepline-gtm meta-skill routing before reading clay-to-deepline recipe docs.
- Validates generated Deepline scripts against Clay ground truth outputs.
- Recipe path: ../deepline-gtm/recipes/clay-to-deepline.md relative to this skill.
Clay To Deepline by the numbers
- 18,569 all-time installs (skills.sh)
- +2,070 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #44 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
clay-to-deepline capabilities & compatibility
- Capabilities
- clay extraction via mcp or scripts · action mapping and script generation · parity validation against clay ground truth · deepline gtm governed session routing
- Works with
- n8n
- Use cases
- orchestration · marketing
What clay-to-deepline says it does
Convert a Clay table configuration into local Deepline scripts.
Handles extraction (MCP or script), documentation, action mapping, script generation, and parity validation
npx skills add https://github.com/code.deepline.com --skill clay-to-deeplineAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 18.6k |
|---|---|
| Repository | code.deepline.com ↗ |
How do I migrate a Clay table workflow into Deepline scripts without losing behavior?
Migrate a Clay table configuration into local Deepline scripts with extraction, action mapping, generation, and parity validation.
Who is it for?
Teams moving GTM enrichment from Clay to Deepline under governed meta-skill sessions.
Skip if: Skip when Clay is not the source system or deepline-gtm is unavailable.
When should I use this skill?
User asks to convert Clay tables to Deepline, migrate Clay workflows, or validate Deepline parity with Clay.
What you get
Generated Deepline scripts mapped from Clay actions and validated against ground truth results.
- Local Deepline scripts
- Parity validation report against Clay
Files
Clay → Deepline Migration
This is a recipe shortcut. It pre-selects the clay-to-deepline recipe but the deepline-gtm governs the entire session.
Execution order
1. Invoke `deepline-gtm` using the Skill tool. 2. 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. 3. Additionally read the clay-to-deepline recipe at ../deepline-gtm/recipes/clay-to-deepline.md (relative to this file) for the specific workflow.
The recipe only covers one part of the task. The meta-skill handles everything else the user asked for.
Related skills
FAQ
Who is clay-to-deepline for?
GTM engineers migrating Clay table automations into Deepline with scripted parity checks.
When should I use clay-to-deepline?
When extracting Clay configs, mapping actions, generating Deepline scripts, and validating against Clay ground truth.
Is clay-to-deepline safe to install?
Review the Security Audits panel on this page before installing in production.