From GTM Skills
Builds Clay tables and enrichment chains using LeadMagic-first waterfalls, Claygent, credit optimization, and CRM push. Use when designing one-time enrichment tables.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gtm-skills:clay-toolkitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Location:** `tools/clay-toolkit` · **Skill name:** `clay-toolkit`
Location: tools/clay-toolkit · Skill name: clay-toolkit
Clay is the operating system for data-driven GTM — spreadsheet-native enrichment, scoring, and CRM push. The mistake: using Clay as a lookup table with one provider and no verify step. This skill covers table architecture, LeadMagic-first waterfalls, Claygent, credit optimization, and output routing.
Clay tool stack:
clay-toolkit (this skill) — one-time tables and waterfallsclay-loops-toolkit — recurring signal loopsclay-automation (automation/) — process and rollout, not column configdomain.leadmagic-toolkit for column wiring.../../outbound/cold-email-copywriting/references/pat-spielmann-outbound-copy.md.clay-loops-toolkit — not mixed into static tables.Trigger phrases: "Clay setup", "Clay waterfall", "Clay enrichment", "Claygent", "Clay table architecture", "Clay automation", "Clay credit optimization", "Clay Sculptor", "Clay formula", "Clay CRM push", "Clay signal table"
For recurring signal monitors → clay-loops-toolkit (tools/clay-loops-toolkit).
For AI column prompts → ai-prompts-toolkit. For rollout process → clay-automation.
Goal: Find email for a list of contacts
Column 1: LeadMagic Email Finder
→ Found? Done.
→ Not found? Fall through to...
Column 2: Apollo Email Finder
→ Found? Done.
→ Not found? Fall through to...
Column 3: ProspectingTool Email Finder
→ Found? Done.
→ Still not found? Flag for manual review.
Load full column specs in references/gtm-table-blueprints.md.
| Blueprint | Rows | Primary Use |
|---|---|---|
| Outbound list | Contacts | Waterfall email → verify → ICP score → CRM |
| Account ABM | Companies | Firmographics → technographics → tier → owner |
| Signal outbound | Contacts | Monitor column → enrich if signal → draft → route |
| CRM hygiene | Contacts | Stale check → re-verify email → update CRM |
| Event follow-up | Contacts | Attendee list → enrich → sequencer within 48h |
Company vs person rule: Always separate tables. Join on domain.
Loops = recurring GTM monitors. Full designs in clay-loops-toolkit.
SOURCE → MONITOR (cheap) → ENRICH (if signal) → ACTION (route)
Common loops: funding, job change, hiring, stale opp, champion move.
references/gtm-table-blueprints.md, then refine in UI.ai-prompts-toolkit P01–P10 — never raw
"find email" without source-url rules.| Output | When | Skill |
|---|---|---|
| HubSpot/SF create/update | Score ≥ threshold | crm-toolkit |
| Smartlead/Instantly webhook | Verified + approved | sequencing-toolkit |
| Slack notify | Tier-1 signal | proactive-alerts |
| n8n webhook | Complex branching, inbound SLA, reply routing | n8n-toolkit |
Push fields: email, first_name, company, icp_score, why_now,
personalization_source, clay_status.
COLUMNS (left to right):
1. INPUT COLUMNS:
- First Name (text)
- Last Name (text)
- Company (text)
- Domain (text or formula: clearbit domain from company)
- LinkedIn URL (optional)
2. ENRICHMENT WATERFALL — EMAIL:
- LeadMagic Find Email (name + company → email)
Credit cost: 1. Confidence: High.
- Apollo Find Email (name + company → email)
Credit cost: 1. Confidence: Medium.
- ProspectingTool (name + domain → email)
Credit cost: 1. Confidence: Medium-Low.
3. VERIFICATION:
- LeadMagic Verify Email (email → status + confidence)
Credit cost: 1. Status: valid/invalid/risky/unknown.
4. ENRICHMENT — PERSON:
- LeadMagic Enrich Person (email → title, company, phone, social)
Credit cost: 2.
5. ENRICHMENT — COMPANY:
- Clearbit Company (domain → employee_count, industry, revenue)
6. SCORING:
- Formula: ICP Score =
(Title matches ICP: 30) +
(Company size 50-500: 20) +
(Email valid: 30) +
(Industry matches: 20)
7. OUTPUT:
- CRM Push (HubSpot / Salesforce)
- Google Sheets sync
- Webhook → n8n → downstream workflows
// Extract domain from email
=RIGHT(Email, LEN(Email) - FIND("@", Email))
// ICP Score calculation
=SUM(
IF(CONTAINS(Title, "VP"), 30, IF(CONTAINS(Title, "Director"), 20, 0)),
IF(AND(Employees > 50, Employees < 500), 20, 0),
IF(Email_Status = "valid", 30, 0),
IF(Industry = "Technology", 20, 0)
)
// Clean company name for domain lookup
=LOWER(SUBSTITUTE(SUBSTITUTE(Company, " ", ""), ",", ""))
// Time since last enrichment (days)
=DATEDIF(Last_Enriched, TODAY(), "D")
The agent delivers a Clay table blueprint and supporting implementation assets:
Before delivering, verify:
references/framework-notes.md — Clay architecture principlestemplates/output-template.md — table design deliverablescripts/check-output.py — validates table blueprint output../../outbound/cold-email-copywriting/references/pat-spielmann-outbound-copy.md — Clay waterfall → copy pipeline, Claygent vs LeadMagic roles (Pat Spielmann)references/gtm-table-blueprints.md — Outbound, ABM, signal, hygiene tablestemplates/waterfall-config.md — provider order per fieldclay-loops-toolkit — Recurring signal loops (funding, job change, hiring)ai-prompts-toolkit — Claygent and LLM column prompts + prompt loopsclay-automation — End-to-end Clay workflow processleadmagic-toolkit — LeadMagic provider in waterfallssequencing-toolkit — Push enriched contacts to sequencerswaterfall-enrichment — Multi-provider waterfall designgtm-role-descriptions — Hire GTM Engineer to own Clay stack (gtm-engineer-hiring.md)npx claudepluginhub leadmagic/gtm-skills --plugin gtm-skillsBuilds Clay enrichment workflows: table architecture, waterfall configuration, Claygent AI research, Sculptor table building, CRM push, and credit optimization. Use for building Clay tables, configuring waterfalls, or automating GTM workflows.
Designs production Clay enrichment pipelines using table schemas, waterfall patterns, and CRM sync flows. Useful for new integrations, data flow reviews, or pipeline standards.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.