Agent skill · product strategy · jeremylongshore
clay-reference-architecture
Design production Clay enrichment pipelines with table schemas, waterfall
Why this skill is useful
Provides detailed integration patterns and table schema designs specific to Clay that the AI wouldn't reliably generate on its own.
What it needs
Requires clay account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay Reference Architecture Overview Production architecture for Clay-based lead enrichment and go-to-market data operations. Covers the three integration patterns (webhook-only, webhook + HTTP API, and full Enterprise API), table schema design, and CRM synchronization flows. Prerequisites Clay account with appropriate plan tier Clear understanding of data volume and enrichment needs CRM integration target (HubSpot, Salesforce, etc.) Defined Ideal Customer Profile (ICP) Instructions Step 1: Choose Your Integration Pattern Step 2: Design Table Schema Standard Lead Enrichment Table: Step 3: Configure Waterfall Pattern Step 4: Implement ICP Scoring Step 5: CRM Sync Architecture Error Handling Issue Cause Solution ------- ------- ---------- Enrichment credits exhausted Too many lookups per row Use conditional runs, connect own API keys Duplicate CRM records No dedup key in CRM push Use email as unique identifier Low email coverage Single provider waterfall Add second provider (Apollo + Hunter) Slow table processing Too many enrichment columns Add conditional runs, order by speed Stale enrichment data No re-enrichment schedule Re-run quarterly on existing contacts Output Document the approved lead-enrichment architecture: data sources and purposes, provider and CRM boundaries, deduplication key, qualification policy, retention and access controls, monitoring, cost guardrails, and incident/rollback owner. Treat a table or CRM sync as production-ready only after its observed records, permissions, and failure behavior match the reviewed design. Examples Build a staging table with synthetic leads, require a valid email and approved ICP threshold before any CRM action, and prove that repeated events update the same CRM record rather than creating duplicates. If enrichment quality or the consent basis is unclear, suppress sync and resolve the data-policy decision before importing the source to production. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-reference-architecture