Skill UI

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.

A comprehensive, expert-level workflow for debugging complex software issues in production environments. This skill guides users through initial triage, advanced observability data collection (APM, distributed traces, logs), intelligent hypothesis generation, and full root cause analysis. Use it when dealing with intermittent failures, performance bottlenecks, or needing a complete fix and prevention plan.

A comprehensive, AI-assisted methodology for diagnosing complex software errors in production environments. This skill guides users through the entire debugging lifecycle, from initial triage and gathering observability data (Sentry, DataDog, Jaeger) to generating hypotheses, selecting appropriate debugging strategies (Time-Travel, Chaos Engineering), and performing AI-powered root cause analysis. It culminates in proposing validated fixes and prevention measures.

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.

This runbook provides a structured guide for responding to critical Guidewire production incidents. It covers the entire lifecycle of incident management, including initial triage (checking monitoring, API errors, and batch logs), diagnosing performance degradation (JVM metrics and query performance), implementing mitigation steps, and proper escalation procedures to Guidewire Support.

Provides an Incident Commander workflow that covers severity triage, timeline reconstruction, runbook generation, communication templates, and post-incident reviews so teams can manage critical SRE/DevOps incidents from detection through resolution.

This skill provides a comprehensive, multi-phase guided workflow for professional incident response management. Following modern SRE principles and the Incident Command System (ICS), it guides users from initial detection and triage (P0-P3 classification) through deep investigation (observability, debugging, security checks), culminating in structured resolution and post-mortem analysis. Use this when managing critical system outages or performance degradation.

A comprehensive guide for troubleshooting and resolving Langfuse-related incidents and outages. It provides step-by-step procedures for initial triage, severity assessment, implementing fallback modes, and resolving common issues like missing traces or rate limits, ensuring continuous observability monitoring for LLM applications.

This runbook serves as a comprehensive guide for responding to incidents within the OpenEvidence platform. It outlines severity levels (P1-P3), step-by-step triage procedures, and mitigation actions, ensuring rapid and structured resolution of API downtime or degradation issues in a healthcare context.

This comprehensive runbook provides step-by-step procedures for rapidly responding to Perplexity API outages and service degradations. It covers initial triage (checking models, auth, DNS), handling common errors (401, 429, 500/503), implementing fallbacks, and structured post-incident activities, including evidence collection and postmortem documentation.