Claude Skill

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.

LLM Mart · 0 points · 11 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download getaero-io-gtm-eng-skills-skills_clay-to-deepline-869569c.zip · 1 KB

getaero-io/gtm-eng-skills 60 12 forks MIT Updated 3d ago

Part of getaero-io/gtm-eng-skills — 17 skills

Install

skills CLI npx skills add https://github.com/getaero-io/gtm-eng-skills/tree/main/skills/clay-to-deepline

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install getaero-io-gtm-eng-skills@llmmart

Git git clone https://github.com/getaero-io/gtm-eng-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole getaero-io/gtm-eng-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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-gtm using 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.

Files (gtm-eng-skills)

skill-metadata.json 187 B

{
  "documents": {
    "SKILL.md": {
      "kind": "entrypoint",
      "title": "Clay → Deepline Migration",
      "tags": [
        "recipe"
      ],
      "providers": []
    }
  }
}

SKILL.md 1.4 KB

---
name: clay-to-deepline
description: "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."
---

# Clay → Deepline Migration

## Quick Start

```bash
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

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. **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.