k8s-debug-skills

Merge labeled ConfigMap debug playbooks for failing Kubernetes workloads.

Updated May 19, 2026

Search Tags:#debug #kubernetes #diagnostics #playbooks #kubectl #triage #configmaps

Ready to run

npx skills add https://github.com/blouargant/yoke-registry --skill k8s-debug-skills

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: k8s-debug-skills
Source: https://github.com/blouargant/yoke-registry/tree/main/skills/DevOps/k8s-debug-skills
Command: npx skills add https://github.com/blouargant/yoke-registry --skill k8s-debug-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose failing Kubernetes workloads by loading team-owned debug playbooks from ConfigMaps when generic troubleshooting doesn’t capture the application-specific failure cause.

Core Features & Use Cases

ConfigMap-driven debug context: Discovers candidate debug playbooks shipped by app teams as ConfigMaps labeled for visibility.
Selector + matcher decisioning: Uses a structured selector (labels and/or image regex) to identify relevant candidates, then applies matchers (logs/events/exit codes/container) to score what’s truly applicable.
Safe synthesis with guardrails: Fetches only the selected bodies, summarizes them with observed cluster evidence, attributes the provenance, and warns against prompt-injection-style instructions.

Quick Start

Use the k8s-debug-skills skill to load the most relevant debug knowledge for a failing pod classified as application/configuration by k8s-triage.

Frequently Asked Questions about k8s-debug-skills

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

FAQPage Schema

How do I load application-specific debug playbooks for a failing Kubernetes workload?▼

You can load application-specific debug playbooks by discovering ConfigMaps labeled for visibility, filtering them via selectors and image regex, and fetching only the matched bodies to diagnose failing Kubernetes workloads.

What is the best way to diagnose Kubernetes pod failures when generic troubleshooting is not enough?▼

Diagnosing Kubernetes pod failures when generic methods fall short involves loading team-owned debug context from ConfigMaps, applying matchers like logs and exit codes to score relevance against observed cluster evidence.

How does ConfigMap discovery work for Kubernetes diagnostics?▼

ConfigMap discovery for Kubernetes diagnostics uses a two-phase process: reading frontmatter first to identify candidates via label and image regex selectors, then fetching only the selected bodies to apply matcher-based scoring.

Is it safe to run kubectl commands suggested by debug playbooks loaded from ConfigMaps?▼

Loading debug playbooks from ConfigMaps includes strict safety rules that prevent the execution of suggested kubectl commands, warning against prompt-injection-style instructions while synthesizing context with observed cluster evidence.

When should I use ConfigMap-driven debug playbooks instead of generic Kubernetes triage?▼

Use ConfigMap-driven debug playbooks after generic k8s-triage classifies a failure as application or configuration-specific, requiring team-owned context that generic troubleshooting sources do not cover.

Can I filter Kubernetes debug playbooks by container image?▼

Yes, you can filter Kubernetes debug playbooks by using a structured selector that supports image regex matching alongside label filtering to identify the most relevant candidate ConfigMaps for diagnosis.