Skill UI

Automates incident postmortem templates for technical documentation, offering structured guidance, best practices, template snippets, and validation cues across API docs, user guides, and architecture narratives.

A comprehensive guide for Site Reliability Engineers (SRE) covering the entire incident lifecycle. It provides structured methodologies for initial severity assessment, establishing an incident command structure, advanced observability-driven investigation (tracing, metrics, logs), systematic troubleshooting, and crucial post-incident root cause analysis (blameless post-mortems). Ideal for managing complex, large-scale system outages.

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 structured playbook for rapidly diagnosing and resolving production incidents related to Lokalise localization services. It guides users through essential quick diagnostics (API health, token validity, rate limits) and provides a decision tree for common failure modes, such as missing or stale translations, API outages, and upload failures, ensuring swift mitigation and postmortem readiness.

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.

This comprehensive guide teaches the best practices for writing effective, blameless postmortem reports following technical incidents. It provides a structured approach to documenting timelines, conducting root cause analysis (RCA), identifying systemic failures, and creating actionable follow-up items. Mastering this skill is crucial for fostering organizational learning and preventing future service disruptions.

This comprehensive runbook provides rapid, structured procedures for incident response on Vast.ai cloud GPU instances. It covers common failure scenarios like spot preemption, training job crashes, and GPU hardware issues. Users can follow the steps for triage, mitigation, recovery, and postmortem analysis to minimize downtime and ensure computational continuity.

A comprehensive, step-by-step guide for responding to Vercel-related production outages, deployment failures, and platform issues. This runbook covers rapid triage using CLI commands, executing instant rollbacks, investigating root causes (log analysis, diffing), managing communication templates, and conducting thorough postmortem reviews.

A forensic tool for performing post-mortem analysis on AI-assisted coding sessions. It goes beyond simply stating what was done, determining *why* work deviated (e.g., spec ambiguity, repo friction, agent error), identifying scope creep, and classifying rework patterns. It provides evidence-backed recommendations to improve prompts, codebase health, and future development workflows.

Automates creating a post-mortem doc, scheduling a review meeting, and notifying the team via Google Chat so incident reviews are centralized and timely.

Comprehensive runbook for managing Adobe API integration outages, covering Firefly, PDF Services, and IMS authentication failures. Provides structured procedures for initial triage, determining severity (P1-P4), executing recovery steps (Auth/Rate Limit), implementing fallback modes, and documenting post-incident reports and communication.

A comprehensive runbook for systematically handling Intercom API outages and integration failures. It guides technical teams through rapid triage (checking status codes, rate limits, and service status), implementing mitigation strategies like graceful degradation, and documenting post-incident reports (postmortem). Essential for maintaining service reliability during Intercom service interruptions.