Skill UI

A structured runbook for handling Apollo.io API outages and production failures. It guides users through severity classification (P1-P4), quick diagnosis scripting, implementing circuit breakers, and graceful degradation strategies to maintain service availability during incidents.

A comprehensive runbook for diagnosing and resolving production incidents involving the Clay SaaS platform. It provides structured triage steps, severity definitions (P1-P4), and resolution guides for issues like credit exhaustion, webhook failures, and data flow outages, ensuring minimal downtime.

A comprehensive guide for engineering teams to manage critical incidents related to Clerk authentication and SaaS platform outages. It covers full incident lifecycle procedures, including initial triage, emergency auth bypass implementation, key rotation, session recovery scripts, and post-incident root cause analysis. Use this when facing production authentication failures or security breaches.

A comprehensive runbook for handling CodeRabbit service outages or malfunctions. It provides step-by-step procedures for quick triage, emergency bypasses (P1), checking installation health (P2), diagnosing delays (P3), and tuning incorrect review behavior (P4). Essential for maintaining continuous CI/CD workflows when the review bot fails.

This guide provides technical patterns for building fault-tolerant integrations with Customer.io. Learn to implement critical resilience techniques, including Circuit Breakers to prevent cascading failures, Retry with Jitter for handling transient errors, and Fallback Queues (using Redis) to ensure data continuity during service outages. Essential for robust, production-grade applications.

A comprehensive runbook designed for on-call engineers to manage Databricks incidents, outages, and major job failures. It provides structured procedures for immediate triage, decision tree guidance (covering cluster failures, code errors, and data quality issues), and steps for evidence collection and postmortem documentation, ensuring rapid and systematic incident resolution.

A comprehensive runbook for standardizing incident response to Deepgram production issues. It guides users through automated triage (checking status, API connectivity, and model performance), severity classification (SEV1-SEV4), and implementing mitigation strategies, including building fallback services and replaying failed requests to ensure business continuity during outages or degradation.

A comprehensive guide for managing Documenso integration incidents. It provides step-by-step procedures for diagnosing and resolving production outages, covering cloud service disruptions, self-hosted database errors, and webhook failures. Essential for on-call engineers to maintain system uptime.

This skill provides patterns for building highly resilient applications that interact with external APIs. It covers crucial concepts like Exponential Backoff with Jitter, request queuing for bulk operations, and the Circuit Breaker pattern. Use this when your application needs to handle rate limit errors (429), transient network failures, or temporary service outages, ensuring reliable throughput and graceful degradation.

This runbook provides comprehensive, step-by-step procedures for managing critical incidents involving Evernote integrations. It covers diagnosing API outages, resolving persistent rate limits, handling authentication failures, and recovering from data synchronization issues. Use this guide during production troubleshooting or service outages to ensure rapid and systematic incident response, including circuit breaker activation and graceful degradation strategies.

A comprehensive runbook providing structured procedures for responding to Exa search API outages and integration failures. It guides users through initial triage, analyzing specific HTTP error codes (e.g., 401, 429, 5xx), implementing mitigation strategies, and completing thorough post-incident reviews and root cause analyses.

A comprehensive runbook providing systematic procedures for responding to Firecrawl API outages and integration failures. It guides technical teams through triage, diagnosis, and mitigation for common issues (e.g., 401, 429, 5xx errors). Includes steps for fallback implementation, evidence collection, and postmortem documentation to ensure rapid service recovery.