gke-ai-troubleshooting-handle-disruption-gpu-tpu SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
gke-ai-troubleshooting-handle-disruption-gpu-tpu 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-ai-troubleshooting-handle-disruption-gpu-tpu@git:20261010.fbd1f7dPins git:20261010.fbd1f7d 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
third_party/google-skills/gke-ai-troubleshooting-handle-disruption-gpu-tpu/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261010.fbd1f7d, committed Oct 10, 2026
- Size
- 6,505 bytes
- Repository stars
- 124
- License
- Apache-2.0
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing node taints, or configuring workload protection strategies (graceful termination, opportunistic maintenance, PodDisruptionBudgets). Don't use for general GKE cluster creation…
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
# Handle Disruption on GPUs and TPUs Troubleshooting
## 🔍 Diagnostic Workflow
### Step 0: Context Acquisition
- **Mandatory**: When a user asks to debug or investigate an actual workload
disruption, node crash, or unexpected restart without providing complete
cluster details, you MUST immediately halt and request all missing mandatory
parameters (`project_id`, `location`, `cluster_name`, `timestamp`) BEFORE
delivering theories or general diagnostic commands. Only skip context
acquisition if the user explicitly requests a generic reusable runbook or
provides a complete static telemetry/log dump for offline analysis.
- **Optional**: `node_name`, `workload_name`, `workload_namespace`,
`nodepool_name`.
### Step 1: [Low Risk] Check for Upcoming Scheduled Maintenance
- **Action**: Propose running `kubectl` to check if nodes have the scheduled
maintenance label indicating an upcoming disruption.
- **Example Command**:
```bash
kubectl get nodes -l cloud.google.com/scheduled-maintenance-time -L cloud.google.com/scheduled-maintenance-time
```
- **Interpretation**: The `SCHEDULED-MAINTENANCE-TIME` column shows the Unix
…Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gke-ai-troubleshooting-handle-disruption-gpu-tpu@sha256:706f73fa33d18d53The line at the top of this page pins the label git:20261010.fbd1f7d, 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_j54dskdpyu7mrr7q)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
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 (6505 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_j54dskdpyu7mrr7q GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gke-ai-troubleshooting-handle-disruption-gpu-tpu GET https://markdownregistry.com/api/v1/blob/706f73fa33d18d53f907851421078494912e613a485ee62d88d273696d3bc34f
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