Agent skill · data analytics · jeremylongshore
clay-advanced-troubleshooting
Deep-debug complex Clay enrichment failures, provider degradation, and
Why this skill is useful
Provides specific debugging scripts and domain knowledge for troubleshooting Clay enrichment failures that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires clay account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay Advanced Troubleshooting Overview Deep debugging techniques for complex Clay issues that resist standard troubleshooting. Covers provider-level isolation, waterfall diagnosis, HTTP API column debugging, Claygent failure analysis, and Clay support escalation with proper evidence. Prerequisites Access to Clay table with the failing enrichments curl and jq for API testing Understanding of Clay's enrichment architecture (providers, waterfall, columns) Browser developer tools for network inspection Instructions Step 1: Isolate the Failure Layer Step 2: Diagnose Enrichment Column Failures In the Clay UI, click on red/error cells to see detailed error messages: Step 3: Debug HTTP API Column Issues Step 4: Debug Claygent Failures Common Claygent issues and diagnosis: Step 5: Build a Support Escalation Package Error Handling Issue Cause Solution ------- ------- ---------- Intermittent enrichment failures Provider rate limiting Reduce concurrent rows, add delay All rows failing suddenly Provider API key expired Reconnect in Settings > Connections Partial data returned Provider has limited coverage Add waterfall fallback provider HTTP API column timeout Target API slow Increase timeout or process async Claygent blocked by website Bot protection Use Navigator mode or different data source Output Produce a redacted escalation packet with environment, table/column scope, symptom, safe correlation IDs, impact metrics, reproducer, containment action, and case owner. Remove webhook URLs, API keys, raw lead/CRM data, and any unapproved screenshots or samples before sharing the packet externally. Examples For a provider-wide failure, first reduce or pause affected automation, compare a synthetic input against the failing job, and collect the sanitized status and time window for support. If the issue only occurs for personal data or a restricted source, do not attach those rows; use a permitted representative or escalate through the data owner. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-advanced-troubleshooting