Agent skill · software engineering · jeremylongshore
clay-debug-bundle
Collect Clay debug evidence for support tickets and troubleshooting.
Why this skill is useful
Adds an executable script for collecting diagnostic information specific to Clay integration issues, which the AI wouldn't generate on its own.
What it needs
Requires curl installed locally. 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 Debug Bundle Current State !node --version 2>/dev/null echo 'N/A' !python3 --version 2>/dev/null echo 'N/A' Overview Collect all diagnostic information needed for Clay support tickets. Clay is a web platform, so debugging focuses on webhook delivery, enrichment column errors, HTTP API responses, and credit consumption -- not pods or clusters. Prerequisites Clay account with access to affected table curl for testing webhook/API connectivity Browser developer tools for capturing network requests Instructions Step 1: Create Debug Bundle Script Step 2: Test Webhook Connectivity Step 3: Capture Environment and Configuration Step 4: Test Enterprise API (If Available) Step 5: Capture Application Logs Step 6: Collect Clay Table Info (Manual Steps) Add to the debug bundle manually from the Clay UI: Step 7: Package and Review Error Handling Item Purpose Included ------ --------- ---------- Webhook connectivity Verify data can reach Clay Automated Environment info Compatibility check Automated Enterprise API test Verify API key validity Automated Application logs Error patterns Automated Table diagnostics Clay-side configuration Manual checklist Config (redacted) Secret management issues Automated Sensitive Data Handling Always redact before submitting: API keys and tokens Email addresses and names from enrichment data Provider API keys (Apollo, Clearbit, etc.) CRM credentials Safe to include: Error messages and HTTP status codes Column names and table structure Credit usage numbers Software versions Output Generate a timestamped, redacted diagnostic archive with collection status, environment, correlation IDs, sanitized configuration, review decision, and support-case reference. The archive must not contain live secrets, raw lead or CRM records, or provider credentials; regenerate rather than manually editing an archive if sensitive data is found. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-debug-bundle--0c2268