clay-incident-runbook
Provides a structured response plan for Clay outages, enrichment failures, and integration incidents.
Install
mkdir -p .claude/skills/clay-incident-runbook && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8983" && unzip -o skill.zip -d .claude/skills/clay-incident-runbook && rm skill.zipInstalls to .claude/skills/clay-incident-runbook
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute Clay incident response procedures for enrichment failures, creditKey capabilities
- →Perform rapid diagnostic triage for Clay platform status
- →Test webhook delivery connectivity and response codes
- →Validate Enterprise API key functionality
- →Execute incident response procedures for credit exhaustion
How it works
The skill provides a bash-based diagnostic script to verify platform status, webhook endpoints, and API keys. It then guides the user through a decision tree to resolve common production failures like credit exhaustion or CRM sync errors.
Inputs & outputs
When to use clay-incident-runbook
- →Triage Clay-related production outages
- →Investigate enrichment failure sources
- →Conduct post-incident reviews
- →Mitigate data flow interruptions
About clay-incident-runbook
This skill provides a runbook for managing production incidents related to Clay. It outlines triage procedures, mitigation strategies for data flow stoppages or service degradation, and steps for conducting post-incident reviews.
Execute Clay incident response procedures with triage, mitigation, and postmortem. Use when responding to Clay-related outages, investigating errors, or running post-incident reviews for Clay integration failures. Trigger with phrases like "clay incident", "clay outage", "clay down", "clay on-call", "clay emergency", "clay broken".
When not to use it
- →General Clay platform usage questions
- →Non-incident related configuration tasks
Prerequisites
Limitations
- →Requires manual configuration of environment variables for full diagnostic coverage
How it compares
Unlike manual troubleshooting, this skill provides a structured, automated triage script and standardized templates for incident communication and postmortems.
Compared to similar skills
clay-incident-runbook side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| clay-incident-runbook (this skill) | 1 | 4mo | Review | Intermediate |
| qa-tester | 29 | 1y | No flags | Intermediate |
| analyzing-logs | 14 | 4mo | Review | Beginner |
| home-assistant-manager | 9 | 11mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
qa-tester
svilupp
Browser automation QA testing skill. Systematically tests web applications for functionality, security, and usability issues. Reports findings by severity (CRITICAL/HIGH/MEDIUM/LOW) with immediate alerts for critical failures.
analyzing-logs
jeremylongshore
Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.
home-assistant-manager
komal-SkyNET
Expert-level Home Assistant configuration management with efficient deployment workflows (git and rapid scp iteration), remote CLI access via SSH and hass-cli, automation verification protocols, log analysis, reload vs restart optimization, and comprehensive Lovelace dashboard management for tablet-optimized UIs. Includes template patterns, card types, debugging strategies, and real-world examples.
distributed-tracing
wshobson
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
service-mesh-observability
wshobson
Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.
sentry
openai
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.