
Gke AI troubleshooting node unresponsive timeout
Diagnose and mitigate GKE TPU or GPU nodes stuck in NotReady / NodeStatusUnknown ("Kubelet stopped posting node status") due to host kernel
- Scripts
- None
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 24.4K
- Last commit
- today
- License
- Apache-2.0
- Listing updated
- today
When your agent uses it
Diagnose and mitigate GKE TPU or GPU nodes stuck in NotReady / NodeStatusUnknown ("Kubelet stopped posting node status") due to host kernel panics, hardware lockups, or disabled node auto-repair. Use when nodes stop heartbeating beyond the node auto-repair threshold and pods remain stuck in Terminating. Don't use for healthy nodes, pod-only application crashes, or routine GKE upgrades.
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
From a static check of its 2 files (15 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Install
Copy the skill folder to ~/.claude/skills/gke-ai-troubleshooting-node-unresponsive-timeout to use it in all your projects:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-node-unresponsive-timeout" ~/.claude/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/gke-ai-troubleshooting-node-unresponsive-timeout inside it instead.
Copy the skill folder to ~/.agents/skills/gke-ai-troubleshooting-node-unresponsive-timeout to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-node-unresponsive-timeout" ~/.agents/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/gke-ai-troubleshooting-node-unresponsive-timeout inside it instead.
Copy the skill folder to ~/.cursor/skills/gke-ai-troubleshooting-node-unresponsive-timeout to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-node-unresponsive-timeout" ~/.cursor/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/gke-ai-troubleshooting-node-unresponsive-timeout inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/google/skills.git --path skills/cloud/gke-ai-troubleshooting-node-unresponsive-timeoutOr copy the folder to ~/.gemini/skills/gke-ai-troubleshooting-node-unresponsive-timeout yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/gke-ai-troubleshooting-node-unresponsive-timeout:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-node-unresponsive-timeout" ~/.copilot/skills/gke-ai-troubleshooting-node-unresponsive-timeout &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/gke-ai-troubleshooting-node-unresponsive-timeout inside it instead.
Get the folder:
git clone --depth 1 https://github.com/google/skills.gitThen copy skills/skills/cloud/gke-ai-troubleshooting-node-unresponsive-timeout into your agent's skills folder as gke-ai-troubleshooting-node-unresponsive-timeout. Agents that support SKILL.md read one folder per skill.
Gke AI troubleshooting node unresponsive timeout FAQ
How do I install Gke AI troubleshooting node unresponsive timeout in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/gke-ai-troubleshooting-node-unresponsive-timeout to use it in all your projects, or to .claude/skills/gke-ai-troubleshooting-node-unresponsive-timeout in one project.
Does Gke AI troubleshooting node unresponsive timeout run scripts?
No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use Gke AI troubleshooting node unresponsive timeout?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
More from google/skills

Google platform decision and setup guidance, loaded on demand from Google's skill catalog
- Open source
- 24.4K GitHub stars

Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services an
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Provides expert guidance on Identity and Access Management (IAM) and authenticating and authorizing to Google Cloud services and APIs, cover
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resour
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter,
- Open source
- 24.4K GitHub stars

Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its
- Open source
- 24.4K GitHub stars