skills.rest
randybias
randybiasCOMMUNITY
Explore all skills by this author →
Website𝕏@randybiasGitHub

k8s-troubleshooter

Diagnose Kubernetes incidents and collect evidence for triage reports.

1|Updated Dec 10, 2025
Search Tags:#automation#reports#troubleshooting#kubernetes#evidence#incident-triage
One-click install
npx skills add https://github.com/randybias/k8s4agents --skill k8s-troubleshooter-randybias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-troubleshooter
Source: https://github.com/randybias/k8s4agents/tree/main/skills/k8s-troubleshooter
Command: npx skills add https://github.com/randybias/k8s4agents --skill k8s-troubleshooter-randybias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, jq, base64, gunzip, helm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Kubernetes incidents are time-sensitive and complex to investigate. This Skill provides a structured, automated approach to triage production issues, preserve evidence, and guide remediation decisions.

Core Features & Use Cases

  • Automated incident triage using available scripts (incident_triage.sh) to generate executive triage cards and markdown reports.
  • Evidence capture of cluster state (nodes, pods, events) and blast-radius assessment to scope impact.
  • Ready-to-follow workflows for pod, network, storage, and Helm issues, plus standard incident reports.

Quick Start

Run the automated triage workflow to generate a triage report and evidence set for the current incident.

Frequently Asked Questions about k8s-troubleshooter

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

FAQPage Schema
How do I troubleshoot Kubernetes pod failures and generate an incident report?▼

Troubleshoot Kubernetes pod failures by running automated scripts that collect cluster evidence, classify blast radius, and output structured executive triage reports for fast remediation.

What is the best way to triage Kubernetes production outages automatically?▼

Triage Kubernetes production outages automatically by executing read-only diagnostics that capture node and pod states, perform root-cause analysis with falsification tests, and generate markdown triage cards.

Does this Kubernetes troubleshooting workflow require Helm and kubectl to run?▼

Yes, the troubleshooting workflow requires kubectl, jq, base64, gunzip, and helm installed in your environment to execute its diagnostic scripts and parse cluster state.

Can I diagnose Kubernetes DNS and network issues without modifying the cluster?▼

Yes, you can diagnose DNS and network issues using strictly read-only diagnostics that query cluster state and events without applying changes to your live environment.

How do I assess the blast radius of a Kubernetes storage problem during an incident?▼

Assess blast radius during a storage incident by running automated evidence capture scripts that scope impact across nodes, pods, and events to classify the severity of the problem.

What is root-cause analysis with falsification tests for Kubernetes incidents?▼

Root-cause analysis with falsification tests systematically validates Kubernetes incident hypotheses by attempting to disprove potential causes, ensuring accurate triage before remediation.

Related Skills

Explore More Software Engineering Skills→
iulianditaiuliandita
2

cluster-health

Run read-only Kubernetes cluster health checks and generate status reports.

Community
Advanced
GuitarAlchemistGuitarAlchemist

setup-matt-pocock-skills

Automate repository configuration for issue tracking, triage labels, and domain documentation.

Official
Intermediate
involvexinvolvex

database-migrations-migration-observability

Monitor database migrations with CDC pipelines, metrics, and alerts.

Community
Advanced
marduk191marduk191
9

differential-review

Identify security-focused findings in code changes using git history and risk scoring.

Community
Advanced