Agent skill · software engineering · jeremylongshore
clay-ci-integration
Configure CI/CD pipelines for Clay integrations with automated testing
Why this skill is useful
Adds a complete CI/CD pipeline configuration with executable scripts for Clay integrations that aren't available in public documentation.
What it needs
Requires gh, node, npm installed locally. Requires github account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay CI Integration Overview Set up CI/CD pipelines for Clay-powered applications. Since Clay is a web platform (not a local service), CI focuses on: (1) testing webhook handler code, (2) validating data transformation logic, (3) checking enrichment data schema compliance, and (4) optional live integration tests against Clay's API. Prerequisites GitHub repository with Actions enabled Clay webhook URL stored as GitHub secret Node.js/Python project with test framework Instructions Step 1: Create GitHub Actions Workflow Step 2: Configure Secrets Step 3: Write Unit Tests for Clay Handlers Step 4: Add Data Schema Validation Step 5: Credit Budget Guard in CI Error Handling Issue Cause Solution ------- ------- ---------- Webhook test fails in CI Secret not configured Add CLAYWEBHOOKURL via gh secret set Tests pass locally, fail in CI Missing mock for Clay calls Use vitest mocks for unit tests Integration test flaky Clay API latency varies Add retry logic, increase timeout Credit waste in CI Test sends too many rows Add MAXROWS guard, use minimal fixtures Output Publish a redacted CI receipt with fixture/schema version, mock and integration results, bounded-row budget result, artifact location, promotion decision, and any exception owner. CI secrets, webhook URLs, provider keys, and raw lead fixtures remain protected and unavailable to untrusted pull-request code. Examples Run schema and mocked callback tests for every pull request, then run a single synthetic integration test only in a protected environment with its scoped secret. Fail the workflow if the row cap, schema, authorization, or data redaction assertion fails; do not retry by increasing quotas or test scope. Resources GitHub Actions Documentation Vitest Documentation Next Steps For deployment patterns, see clay-deploy-integration.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-ci-integration