Diagnose GKE TPU VM instances stuck in Compute Engine repair (REPAIRING state) after host errors, maintenance events, or faulty host reports in single-host, multi-host, dynamic slicing, and TPU All Capacity mode node pools. Use when TPU instances in a slice node pool remain in REPAIRING, host error events appear in audit logs, or TPU slices are unschedulable due to a VM in repair.
Install
npx skills add google/skills --skill gke-ai-troubleshooting-tpu-vm-repair-stucknpx skills add google/skills --skill gke-ai-troubleshooting-tpu-vm-repair-stuck -a claude-code -gnpx skills add google/skills --skill gke-ai-troubleshooting-tpu-vm-repair-stuck -a codex -ggemini skills install https://github.com/google/skills.git --path skills/cloud/gke-ai-troubleshooting-tpu-vm-repair-stuckgh skill install google/skills gke-ai-troubleshooting-tpu-vm-repair-stuckgit clone --depth 1 https://github.com/google/skills /tmp/google__skills
mkdir -p ~/.claude/skills ~/.agents/skills
cp -R /tmp/google__skills/skills/cloud/gke-ai-troubleshooting-tpu-vm-repair-stuck ~/.claude/skills/gke-ai-troubleshooting-tpu-vm-repair-stuck # Claude Code
cp -R /tmp/google__skills/skills/cloud/gke-ai-troubleshooting-tpu-vm-repair-stuck ~/.agents/skills/gke-ai-troubleshooting-tpu-vm-repair-stuck # Codex, Cursor, Gemini CLI, Copilot, OpenCode