k8s-troubleshooter

Diagnose Kubernetes pod failures and node issues with structured troubleshooting workflows.

16|4|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/idchain-world/id-agents --skill k8s-troubleshooter-idchain-world
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-troubleshooter
Source: https://github.com/idchain-world/id-agents/tree/main/configs/agents/devops/skills/k8s-troubleshooter
Command: npx skills add https://github.com/idchain-world/id-agents --skill k8s-troubleshooter-idchain-world

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Systematic Kubernetes troubleshooting and incident response workflows to diagnose and resolve cluster issues quickly.

Core Features & Use Cases

  • Structured namespace and pod diagnostics with automated recommendations.
  • Incident response playbooks and references for common Kubernetes issues.
  • Quick-start runbooks and command examples to accelerate remediation.

Quick Start

Describe the Kubernetes issue you want diagnosed and ask the skill for a step-by-step diagnostic plan.

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 CrashLoopBackOff and ImagePullBackOff errors?▼

This skill diagnoses Kubernetes pod failures like CrashLoopBackOff and ImagePullBackOff through structured troubleshooting workflows, providing step-by-step remediation plans across your namespaces and deployments.

What is the best way to diagnose OOMKilled and Pending pods in a production cluster?▼

The best way to diagnose OOMKilled and Pending pods is through systematic Kubernetes incident response playbooks that evaluate resource constraints and node scheduling issues across production namespaces.

How do I resolve NotReady nodes and networking issues in Kubernetes?▼

You resolve NotReady nodes and networking issues in Kubernetes by following structured diagnostic workflows that inspect cluster node conditions and network configurations to isolate infrastructure failures.

Can I use kubectl commands for incident response on production Kubernetes deployments?▼

Yes, you can use kubectl commands for incident response on production Kubernetes deployments, utilizing quick-start runbooks and command examples to accelerate diagnostics and remediation across affected namespaces.

Does this Kubernetes diagnostics skill work for storage issues across multiple namespaces?▼

Yes, this Kubernetes diagnostics skill handles storage issues across multiple namespaces, applying structured troubleshooting workflows to identify and resolve persistent volume claims and storage class configurations.

k8s-troubleshooter: what common Kubernetes incidents does it support?▼

k8s-troubleshooter supports common Kubernetes incidents including pod failures, NotReady nodes, and networking or storage issues. It applies structured diagnostics to production clusters facing CrashLoopBackOff, ImagePullBackOff, OOMKilled, and Pending pods.