sos-emergency

Run emergency recovery procedures for Kubernetes clusters, Talos nodes, and Synology Container Manager.

4|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/kingdon/skills --skill sos-emergency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sos-emergency
Source: https://github.com/kingdon/skills/tree/main/.github/skills/sos-emergency
Command: npx skills add https://github.com/kingdon/skills --skill sos-emergency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, talosctl, and includes scripts (resource) components.

What problem does it solve?

This skill provides emergency recovery procedures for Kubernetes clusters, Talos nodes, and Synology Container Manager environments, enabling rapid restoration during outages or live-stream incidents.

Core Features & Use Cases

  • Comprehensive recovery playbooks for Kubernetes/Talos environments, including etcd quorum recovery, Talos resets, and container manager access.
  • Step-by-step diagnostic and remediation workflows designed for live debugging and rapid restoration.
  • Use Case: When a cluster becomes unresponsive during a live stream, trigger /sos to initiate automated diagnostics and guided recovery actions.

Quick Start

Use the /sos slash command to trigger the emergency diagnostic workflow and begin the recovery sequence on the affected cluster. If prompted, follow on-screen guidance to perform resets, checks, and safe shutdown procedures.

Frequently Asked Questions about sos-emergency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover a Kubernetes cluster when etcd loses quorum?

To recover a Kubernetes cluster when etcd loses quorum, this skill runs a predefined diagnostic script to assess connectivity and guides you through scripted, auditable steps to restore etcd quorum and validate cluster health.

What steps are involved in a Talos node reset for emergency cluster recovery?

A Talos node reset for emergency cluster recovery involves triggering the /sos diagnostic workflow to evaluate the node state, then following guided command sequences using talosctl to safely reset and rejoin the affected node.

Do I need kubectl and talosctl installed to run emergency diagnostics on my cluster?

Yes, you need kubectl and talosctl installed to run emergency diagnostics, as this skill depends on these tools to execute its predefined diagnostic scripts and perform remediation workflows on Kubernetes and Talos environments.

What is the best way to run live debugging diagnostics during a Kubernetes outage?

The best way to run live debugging diagnostics during a Kubernetes outage is to trigger the /sos slash command, which initiates an automated diagnostic workflow to perform connectivity checks and guide remediation.

Can I use this emergency recovery workflow to perform a controlled shutdown of Synology Container Manager?

Yes, you can use this emergency recovery workflow to perform a controlled shutdown of Synology Container Manager environments, as it provides specific recovery procedures and guided actions for managing container manager access during outages.

Why does my Kubernetes cluster become unresponsive during a live stream and how is it handled?

Kubernetes clusters can become unresponsive during live streams due to node failures or etcd issues; this skill handles it by enforcing scripted, auditable recovery steps with validation checks to ensure rapid restoration.