What is the Clay Incident Runbook skill?

It is a specialized Claude Code capability designed to guide developers through the triage, mitigation, and reporting of issues related to Clay integrations and outages.

What triggers this skill in Claude Code?

You can trigger it using natural language phrases such as 'clay outage', 'clay incident', 'clay is broken', or 'clay on-call'.

Does it support post-incident analysis?

Yes, it includes procedures for evidence collection and uses a postmortem template to document the root cause and resolution steps for future reference.

Can this skill interact with my Kubernetes infrastructure?

Yes, it is authorized to use tools like kubectl to check pod logs, status endpoints, and cluster health during an investigation.

How does it help with rate limiting (429 errors)?

The skill provides specific instructions to check rate limit headers and enables request queuing procedures to manage traffic until limits reset.

Clay Incident Runbook

Name: Clay Incident Runbook
Author: micsapp

bymicsapp

0•

Analytics & Monitoring

Automates and guides incident response for Clay integrations through standardized triage, mitigation, and postmortem procedures.

The Clay Incident Runbook skill provides a comprehensive framework for managing outages and errors within Clay-based workflows. It streamlines the incident response lifecycle by helping developers categorize severity levels, perform rapid triages using kubectl and curl, and execute immediate remediation actions for common API errors like 401s, 429s, and 503s. By integrating status page checks with internal metrics, this skill ensures that teams can differentiate between local configuration issues and global provider outages while maintaining consistent communication through built-in Slack and PagerDuty templates.

Key Features

01Pre-formatted communication templates for internal and external stakeholders

02Standardized P1-P4 severity level classification for Clay incidents

03Step-by-step remediation for authentication, rate-limiting, and server errors

04Automated triage workflows using status checks and system metrics

05Postmortem evidence collection and documentation generation

060 GitHub stars

Use Cases

01Managing team-wide communication and status updates during critical production downtime

02Automating secret rotation and pod restarts during 401/403 authentication failures

03Identifying if a service failure is a local credential issue or a global Clay API outage

Key Features

01Pre-formatted communication templates for internal and external stakeholders

02Standardized P1-P4 severity level classification for Clay incidents

03Step-by-step remediation for authentication, rate-limiting, and server errors

04Automated triage workflows using status checks and system metrics

05Postmortem evidence collection and documentation generation

060 GitHub stars

Use Cases

01Managing team-wide communication and status updates during critical production downtime

02Automating secret rotation and pod restarts during 401/403 authentication failures

03Identifying if a service failure is a local credential issue or a global Clay API outage