gke-workload-troubleshooting SKILL.md skillA
gke-workload-troubleshooting from gke-labs/kube-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gke-labs/kube-agents/gke-workload-troubleshooting@git:20261027.077d654Pins git:20261027.077d654 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gke-labs/kube-agents
- Path
agents/cluster/skills/gke-workload-troubleshooting/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261027.077d654, committed Oct 27, 2026
- First version recorded
- Jul 28, 2026
- Size
- 9,715 bytes
- Repository stars
- 124
- License
- Apache-2.0
Systematic Standard Operating Procedure (SOP) for diagnosing GKE workload failures, crash loops, resource OOMs, mounting errors, and connectivity timeouts.
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
# GKE Workload Troubleshooting Skill Use this skill to systematically diagnose and resolve failures in application workloads deployed in GKE clusters. This skill enforces a read-only diagnostics boundary before proposing manifest or config corrections. ## 🔍 Diagnostic Workflow ### Step 0: Context Acquisition & Time Window Definition To begin troubleshooting, acquire the following context from the user or active `SETTINGS.md` config: - **Project ID** (e.g., `my-gcp-project`) - **Cluster Name** (e.g., `my-gke-cluster`) - **Cluster Location** (e.g., `us-central1`) - **Workload Name** (e.g., `payment-api`) - **Workload Namespace** (e.g., `checkout`) - **Issue Time** (Optional, e.g., `2026-06-01T15:30:00Z`) Before running any diagnostics or `kubectl` commands, you **must** fetch GKE credentials and context for the target GKE cluster: ```bash gcloud container clusters get-credentials <cluster_name> --region <cluster_location> ``` #### Time Handling & Fallbacks: 1. **Determine Issue Timestamp ($T$)**: - **Specific Time Provided**: If the user provides a specific timestamp, use it as $T$. …
Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gke-workload-troubleshooting@sha256:67f1106822eacdebThe line at the top of this page pins the label git:20261027.077d654, 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.
[](https://markdownregistry.com/a/art_iw4ag2dhz364eqdz)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 28, 2026 and Oct 27, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.077d654 latest | 2026-10-27 | 077d654 | 9,715 B | A | view · diff |
| git:20260909.eb89697 | 2026-09-09 | eb89697 | 9,648 B | A | view · diff |
| git:20260904.e20318d | 2026-09-04 | e20318d | 9,482 B | A | view · diff |
| git:20260821.10730d8 | 2026-08-21 | 10730d8 | 9,472 B | A | view · diff |
| git:20260812.8e8a46c | 2026-08-12 | 8e8a46c | 9,294 B | A | view · diff |
| git:20260728.aca5b5c | 2026-07-28 | aca5b5c | 9,025 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9715 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
gke-labs/kube-agents · 124 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iw4ag2dhz364eqdz GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gke-workload-troubleshooting GET https://markdownregistry.com/api/v1/blob/67f1106822eacdebe6ab82e3027cd37165c827d00cc744a97905f8bdb6afae47
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 gke-labs/kube-agents
Every file in gke-labs/kube-agents