Skill UI

A comprehensive operational runbook for managing outages and errors related to Mistral AI integrations. It provides structured procedures, including severity classification, quick API health checks, decision trees for common errors (401, 429, 5xx), immediate mitigation steps, and post-incident evidence collection and reporting.

A structured framework for managing production outages using Sentry. This guide walks users through classifying incident severity (P0-P3), performing deep triage using stack traces and breadcrumbs, and executing API-based queries to pinpoint root causes and measure impact. Essential for DevOps and SRE teams during critical incident response.

This powerful tool generates comprehensive operational runbooks from a service name. It structures critical workflows, including deployment, incident response, maintenance, and rollback procedures. It is essential for standardizing on-call procedures, ensuring consistent incident handling across teams, and quickly documenting services before production launch.

A comprehensive runbook for rapid incident response to Figma REST API failures. It guides users through quick triage (checking status, authentication, rate limits), decision-making based on error codes (403, 429, 500), applying immediate mitigation strategies (token rotation, fallback modes), and completing thorough postmortem documentation.

A comprehensive runbook for diagnosing and resolving outages, degradation, and rate-limiting issues when using the Claude API. It provides structured triage steps, decision trees, and mitigation strategies for P1 through P4 severity incidents, ensuring minimal downtime and stable API interaction.

A comprehensive runbook providing structured guidance for rapid incident response when encountering failures with the Canva Connect API integration. It guides users through initial triage (checking status, error rates), outlines immediate mitigation strategies for common API errors (401, 429, 5xx), and covers standardized communication templates and detailed post-incident procedures, including log collection and root cause analysis.

A comprehensive, step-by-step runbook designed for diagnosing and resolving critical operational issues in ClickHouse databases. Covers tiered severity levels (P1-P3) for scenarios ranging from server outages and OOM kills to performance degradation and stuck queries. Provides essential system tables queries and commands for service recovery and system health checks.

This runbook provides structured steps for responding to critical production incidents on the CoreWeave platform. Use it when dealing with GPU workload failures, inference service outages, or general Kubernetes resource issues. It guides users through checking pod status, node health, and diagnosing common model loading errors to ensure rapid service recovery.

A comprehensive runbook for responding to critical incidents involving Flexport API integrations. It covers various failure scenarios, including complete API outages, webhook delivery loss, and complex supply chain data synchronization issues. The guide provides severity classification (P1-P4), diagnostic commands, and step-by-step playbooks for rapid triage and mitigation.

This comprehensive runbook provides detailed procedures for diagnosing and resolving critical incidents within the Glean enterprise search platform. It covers all severity levels (P1-P4) and failure modes, including API outages, connector synchronization failures, indexing backlogs, and permission drift. It includes diagnostic steps, advanced troubleshooting playbooks, and communication templates for technical support and engineering teams.

A comprehensive runbook for managing HubSpot CRM integration failures. It guides users through rapid triage, diagnosing common API errors (401, 429, 5xx), implementing immediate mitigation steps, and completing structured post-incident reviews. Essential for maintaining system uptime during outages.

A comprehensive guide for rapid incident response and troubleshooting of Miro API v2 integration failures. It covers defining severity levels, quick triage steps, detailed error handling for 4xx/5xx status codes (e.g., token expiration, rate limiting), mitigation strategies, and postmortem evidence collection.