Skill UI

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.

A comprehensive runbook for rapid incident response concerning Ideogram API outages, authentication failures, and performance degradation. It provides detailed triage scripts, decision flows based on HTTP status codes (401, 429, 5xx), immediate mitigation actions (e.g., enabling fallback mode), and structured templates for communication and postmortems.

This comprehensive runbook provides step-by-step procedures for managing MaintainX integration failures. It guides users through severity classification, immediate triage, root cause analysis, and mitigation strategies (such as key rotation or request buffering). The playbook ensures systematic incident response, verification of recovery, and proper post-mortem documentation for rapid system restoration.

A structured guide for conducting blameless post-mortem reviews after any security incident. This process helps identify root causes using techniques like the 5 Whys, calculates critical metrics (MTTD, MTTR), and generates actionable recommendations to continuously improve incident response playbooks and procedures.

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

A comprehensive guide for rapid incident response for Palantir Foundry systems. This runbook provides structured steps for triage, severity classification (P1-P4), and detailed playbooks for common issues like authentication failures, rate limiting, and build pipeline errors. It guides users through investigation, mitigation, and postmortem documentation to minimize downtime and ensure quick recovery.

A comprehensive operational guide for managing Salesforce integration failures and outages. This runbook provides step-by-step procedures for initial triage, diagnosing common API errors (e.g., rate limiting, authentication failures), implementing mitigation strategies, and conducting detailed post-incident reviews (postmortems). It covers best practices for ensuring system reliability during critical system outages.

Generates a comprehensive, structured, and blameless incident postmortem document. This skill is designed for Root Cause Analysis (RCA), P1/P2 incident reviews, and outage reports, ensuring the focus remains on systemic gaps and preventative action items rather than individual blame. It guides the user through gathering all necessary details, from the timeline and impact to defining concrete action owners and due dates.

Provides a comprehensive framework for generating structured, blameless post-mortem documents after a production outage or service degradation. It guides teams through reconstructing timelines, identifying root causes using methods like 5 Whys, quantifying impact, and generating concrete, actionable preventative measures to improve system resilience.