debug-cluster SKILL.md skillA

debug-cluster from tanguille/cluster is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add tanguille/cluster/debug-cluster@git:20261014.1b8131c

Pins git:20261014.1b8131c in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: tanguille/cluster
Path: .agents/skills/debug-cluster/SKILL.md
Versions recorded: 6
Latest version: git:20261014.1b8131c, committed Oct 14, 2026
First version recorded: Jun 8, 2026
Size: 3,071 bytes
Repository stars: 15
License: MIT

Diagnose and resolve Kubernetes cluster issues using structured fact gathering and 5-Whys root cause analysis. user: "pod CrashLoopBackOff" → describe pod, logs, events; GitOps fix in repo user: "HelmRelease not reconciling" → flux get/describe, reconcile with source user: "service unreachable" → endpoints, HTTPRoute, workload health user: "backup mover failing" → often delegate with backup-restore context Use for pod failures, OOM, Flux reconciliation failures, unreachable services, or node…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Debug cluster

Structured debugging with parallel fact gathering; delegate deep 5-Whys or log mining to subagents when useful.

## Quick diagnosis

**Parallel gather:**

- Kubernetes resources (pods, deployments, services, events)
- Logs (current + previous containers)
- Flux instance when GitOps-related
- Historical/crashed-pod logs and firing alerts: `grafana_*` / `victorialogs-mcp_*` tools via the unified vMCP (`find_tool`/`call_tool`)

```bash
kubectl get pods -n <ns> -o wide
kubectl get events -n <ns> --sort-by='.lastTimestamp'
kubectl describe pod <pod> -n <ns>
```

## Symptom map

| Symptom | Check |
|---------|-------|
| CrashLoopBackOff | describe, logs, previous container |
| OOMKilled | exit code 137, limits |
| ImagePullBackOff | image, registry auth, pull secrets |
| Pending | node resources, taints, PV binding |
| Flux stuck | `flux get all -A`, GitRepository status |

## 5-Whys subagent

When root cause is unclear, spawn a subagent with gathered facts and ask for five whys ending in a GitOps-fixable cause (config typo, wrong secret ref, chart values, etc.).

## Fix patterns (GitOps first)

| Issue | Fix |
|-------|-----|
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add tanguille/cluster/debug-cluster@sha256:af72869a17d34b65

The line at the top of this page pins the label git:20261014.1b8131c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_maix527fyjmk2xgc.svg)](https://markdownregistry.com/a/art_maix527fyjmk2xgc)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 6 versions of this file, between Jun 8, 2026 and Oct 14, 2026, about one every 26 days.

version	committed	commit	size	audit
git:20261014.1b8131c latest	2026-10-14	1b8131c	3,071 B	A	view · diff
git:20260928.2939037	2026-09-28	2939037	3,017 B	A	view · diff
git:20260911.093c4fb	2026-09-11	093c4fb	4,181 B	A	view · diff
git:20260712.722c938	2026-07-12	722c938	4,256 B	A	view · diff
git:20260711.18776f8	2026-07-11	18776f8	4,241 B	A	view · diff
git:20260608.c6d6a1a	2026-06-08	c6d6a1a	4,121 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3071 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

tanguille/cluster · 15 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_maix527fyjmk2xgc
GET https://markdownregistry.com/api/v1/resolve?ref=tanguille/cluster/debug-cluster
GET https://markdownregistry.com/api/v1/blob/af72869a17d34b6541399cf7f8af8b8c381174bd1145051975c0d4a5935ae3f0

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from tanguille/cluster

add-app-to-cluster SKILL.md skill

tanguille/cluster · .agents/skills/add-app-to-cluster/SKILL.md · Deploy new applications to the Kubernetes cluster via FluxCD GitOps. Creates HelmReleases, Kustomizations, and…