Agent skill · software engineering · jeremylongshore
clay-multi-env-setup
Configure Clay integrations across development, staging, and production
Why this skill is useful
Provides specific environment configuration patterns and scripts for managing Clay integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires clay account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay Multi-Environment Setup Overview Configure Clay integrations across dev/staging/prod with isolated tables, separate webhook URLs, and environment-specific enrichment settings. Clay is a single workspace per account, so multi-environment isolation requires separate tables, careful naming, and environment-aware application code. Prerequisites Clay account (one workspace can hold multiple tables) Environment variable management per deployment target Understanding of Clay table and webhook concepts Instructions Step 1: Create Per-Environment Tables In Clay, create separate tables for each environment: Table Name Environment Webhook URL Auto-Enrich Credit Cap ------------ ------------- ------------- ------------- ------------ [DEV] Outbound Leads Development Dev webhook ON (small batches) 100 rows [STG] Outbound Leads Staging Staging webhook ON 500 rows Outbound Leads Production Prod webhook ON 10,000 rows Each table gets its own webhook URL. Copy each URL to the appropriate environment's secrets. Step 2: Environment Configuration Step 3: Environment Variable Management Step 4: Startup Validation Step 5: Environment-Aware Safety Guards Error Handling Issue Cause Solution ------- ------- ---------- Wrong table receives data Dev webhook URL in production Validate webhook URL matches environment Dev data in production CRM CRM sync enabled in dev Guard CRM sync to production only Credit waste in dev/staging Full enrichment on test data Set low row caps on dev/staging tables Missing webhook URL at startup Environment variable not set Add startup validation with Zod Output Create an environment-bound configuration record listing the workspace/table prefix, secret references, row and credit limits, CRM permission, validation result, deployment owner, and tested promotion/rollback path. Never share actual webhook URLs, API keys, provider credentials, or production lead data in environment files, examples, or diagnostics. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-multi-env-setup