CL

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.zip

Installs 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, credit
73 charsno explicit “when” trigger
Intermediate

Key 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

You give it
Incident trigger phrase or diagnostic command
You get back
Triage report and incident resolution steps

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

CLAY_WEBHOOK_URLCLAY_API_KEYCLAY_CALLBACK_URL

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.

SkillInstallsUpdatedSafetyDifficulty
clay-incident-runbook (this skill)14moReviewIntermediate
qa-tester291yNo flagsIntermediate
analyzing-logs144moReviewBeginner
home-assistant-manager911moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore →

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

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.

29113

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

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.

9110

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.

577

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.

574

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`.

1048

Search skills

Search the agent skills registry