Agent skill · operations · jeremylongshore
clay-incident-runbook
Execute Clay incident response procedures for enrichment failures, credit
Why this skill is useful
Adds a complete executable incident response script for Clay outages and enrichments that provides specific diagnostic commands and workflows not commonly known.
What it needs
Requires bash 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 Incident Runbook Overview Rapid response procedures for Clay-related production incidents. Clay is a hosted SaaS platform, so incidents fall into two categories: (1) Clay-side issues (platform outage, provider degradation) and (2) your-side issues (webhook misconfiguration, credit exhaustion, handler failures). Prerequisites Named incident commander, service/data owners, and escalation contacts Access to redacted telemetry, queue state, table configuration, and runbooks A tested ability to pause enrichment, CRM sync, and webhook intake Approved communications and evidence-retention procedures Severity Levels Level Definition Response Time Examples ------- ------------ --------------- ---------- P1 Complete data flow stopped < 15 min Credits exhausted, webhook URL expired, Clay outage P2 Degraded enrichment < 1 hour Low hit rates, slow processing, CRM sync errors P3 Minor impact < 4 hours Single provider down, intermittent webhook failures P4 No user impact Next business day Monitoring gaps, cost optimization needed Instructions Step 1: Quick Triage (2 Minutes) Step 2: Decision Tree Step 3: Common Incident Resolutions P1: Credits Exhausted P1: Webhook URL Expired (50K Limit) P2: Low Enrichment Hit Rate P2: CRM Sync Failures Step 4: Communication Template Step 5: Postmortem Template Item Details ------ --------- Incident Date [Date] Duration [X hours] Severity P[1/2/3] Impact [Leads not enriched / CRM not updated / Credits exhausted] Root Cause [e.g., Webhook hit 50K limit without monitoring] Detection [How was it discovered? Alert / user report / manual check] Resolution [Steps taken] Credits Lost [Estimate of wasted credits, if any] Prevention [Monitoring gaps to close, safeguards to add] Error Handling Issue Cause Solution ------- ------- ---------- Can't access Clay dashboard Browser/network issue Try incognito, different browser, or mobile Webhook test returns nothing Webhook URL malformed Re-copy full URL from Clay table All providers returning empty Accoun …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-incident-runbook--0a9371