
Gke AI troubleshooting tpu metrics monitoring
Monitors GKE TPU nodes, node pools and workloads using system metrics and PromQL
- Scripts
- shell
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 24.4K
- Last commit
- 2 days ago
- License
- Apache-2.0
- Listing updated
- 1 day ago
Similar skills
About Gke AI troubleshooting tpu metrics monitoring
Gke AI troubleshooting tpu metrics monitoring is an open-source agent skill for cloud and infrastructure. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.
This skill guides an agent through watching Google Kubernetes Engine clusters that run TPU accelerators. It checks whether a workload is set up to export runtime metrics, then reads TensorCore duty cycle, TPU memory and utilization figures from Cloud Monitoring for both containers and nodes.
The workflow goes beyond accelerator usage. It queries node readiness conditions, multi-host TPU node pool status and availability, and interruption counts broken down by type and reason, including host maintenance events. It also includes PromQL to derive mean time to recovery and mean time between interruptions over a seven-day window, which helps determine whether a slowdown or stop comes from the underlying infrastructure.
The guide expects a GCP project, a GKE cluster name and location, and optionally a node or node pool name, which the agent can look up with its own cloud tools. Queries are written for Cloud Monitoring and the steps assume GKE system metrics are enabled. The skill ships with bash scripts and a usage attribution reference file.
When your agent uses it
Monitors and troubleshoots GKE TPU workloads, nodes, and node pools using GKE system metrics and PromQL. Use when monitoring TensorCore duty cycle, TPU memory, node readiness, multi-host TPU node pool availability, host maintenance or preemption interruptions, and calculating MTTR or MTBI metrics for GKE TPUs. Don't use for general non-TPU GKE workload monitoring or non-metric TPU debugging.
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
- Runs shell scripts(see the files on GitHub)
- No network calls found in its scripts(see the files on GitHub)
- License: Apache-2.0(see the files on GitHub)
From a static check of its 4 files (11 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.
Check another skill before you install it.
Install
Copy the skill folder to ~/.claude/skills/gke-ai-troubleshooting-tpu-metrics-monitoring 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-tpu-metrics-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-metrics-monitoring" ~/.claude/skills/gke-ai-troubleshooting-tpu-metrics-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/gke-ai-troubleshooting-tpu-metrics-monitoring inside it instead.
Copy the skill folder to ~/.agents/skills/gke-ai-troubleshooting-tpu-metrics-monitoring 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-tpu-metrics-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-metrics-monitoring" ~/.agents/skills/gke-ai-troubleshooting-tpu-metrics-monitoring &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/gke-ai-troubleshooting-tpu-metrics-monitoring inside it instead.
Copy the skill folder to ~/.cursor/skills/gke-ai-troubleshooting-tpu-metrics-monitoring 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-tpu-metrics-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-metrics-monitoring" ~/.cursor/skills/gke-ai-troubleshooting-tpu-metrics-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/gke-ai-troubleshooting-tpu-metrics-monitoring 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-tpu-metrics-monitoringOr copy the folder to ~/.gemini/skills/gke-ai-troubleshooting-tpu-metrics-monitoring yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/gke-ai-troubleshooting-tpu-metrics-monitoring:
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-tpu-metrics-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-metrics-monitoring" ~/.copilot/skills/gke-ai-troubleshooting-tpu-metrics-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/gke-ai-troubleshooting-tpu-metrics-monitoring inside it instead.
Get the folder:
git clone --depth 1 https://github.com/google/skills.gitThen copy skills/skills/cloud/gke-ai-troubleshooting-tpu-metrics-monitoring into your agent's skills folder as gke-ai-troubleshooting-tpu-metrics-monitoring. Agents that support SKILL.md read one folder per skill.
What it does
- Runtime metrics setup check
- Verifies pod ports, JAX version, GKE version and system metrics settings needed for TPU metric export.
- TPU utilization metrics
- Reads duty cycle, memory usage and tensorcore utilization for TPU containers and nodes.
- Node readiness queries
- Lists PromQL checks for whether TPU nodes are Ready and surfaces non-Ready conditions.
- Multi-host node pool availability
- Tracks node pool status and whether all hosts in a multi-host TPU pool are available.
- Interruption analysis
- Breaks down maintenance, preemption and termination events by type and reason.
- Recovery and interruption metrics
- Calculates mean time to recovery and mean time between interruptions over seven days.
Good for
- Check whether a stalled TPU training job lost a node to maintenance
- See how busy the TensorCores are on a GKE TPU cluster
- Confirm that a multi-host TPU node pool has all hosts available
- Measure recovery time and interruption frequency for TPU nodes
- Find which node pools had recent preemption or host maintenance events
Gke AI troubleshooting tpu metrics monitoring FAQ
Which environment does this skill need?
It needs a GCP project, a GKE cluster name and location, and optionally node or node pool names. The queries run against Cloud Monitoring with GKE system metrics enabled.
Does the skill change any cluster resources?
Its steps are read-only metric queries and configuration checks. It does not describe making changes to the cluster.
Which GKE versions are required?
The guide lists minimums: GKE 1.27.4-gke.900 or later for runtime metrics, 1.28.1-gke.1066000 or later for host metrics, and 1.32.1-gke.1357001 or later for node status conditions.
When should it not be used?
According to its description, it should not be used for general non-TPU GKE workload monitoring or for TPU debugging that does not involve metrics.
How do I install Gke AI troubleshooting tpu metrics monitoring in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/gke-ai-troubleshooting-tpu-metrics-monitoring to use it in all your projects, or to .claude/skills/gke-ai-troubleshooting-tpu-metrics-monitoring in one project.
Does Gke AI troubleshooting tpu metrics monitoring run scripts?
Yes. It runs shell scripts. No network calls were found in its 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 tpu metrics monitoring?
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.
What are the best alternatives to Gke AI troubleshooting tpu metrics monitoring?
The closest alternatives to Gke AI troubleshooting tpu metrics monitoring are Gke AI troubleshooting tpu performance degradation, Gke AI troubleshooting handle disruption GPU tpu, Gke AI troubleshooting tpu reservation stockout, Gke AI troubleshooting node unresponsive timeout and Aks GPU inference.
Where this comes from
- Description: from the skill's own SKILL.md.
More from google/skills

Route platform choices to Google's own skills by fetching and filtering its skill catalog
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Guardrails for gcloud commands: validate syntax with help, scope projects, dry-run first
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Authenticate to Google Cloud: ADC, impersonation, service accounts and IAM roles
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

First-time Google Cloud setup: sign in, pick a project, link billing, with consent gates
- Open source
- 24.4K GitHub stars
- Cloud and infrastructure

Look up Google developer docs through the Developer Knowledge MCP server or REST fallback
- Open source
- 24.4K GitHub stars
- Developer tools

Add, remove or clear audience members with the Google Data Manager API
- Open source
- 24.4K GitHub stars
- Marketing and SEO



