
Gke AI troubleshooting tpu dynamic slices monitoring
Inspect, troubleshoot and validate GKE TPU dynamic slice resources and workloads
- 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 dynamic slices monitoring
Gke AI troubleshooting tpu dynamic slices 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 helps an agent check the lifecycle state of GKE TPU Dynamic Slice custom resources and interpret their status conditions against a reference table of states such as provisioning, active, degraded and failed. When a slice fails to provision, it walks through a checklist covering node existence and allocation, topology alignment with partition count, and reservation block consistency.
It also reviews workload manifests meant for dynamic slices, checking the required annotations and node selectors for single-slice pods and the extra JobSet exclusive-topology annotation for multi-slice deployments. For slices stuck in deletion, it describes removing finalizers with a JSON patch and warns about possibly orphaned VM, network or accelerator resources. Disabling the slice controller and cleaning up CRDs and node labels is also covered.
The workflow relies on kubectl and gcloud configured against the target GKE cluster, with Cloud Logging enabled on the project. Destructive steps such as patching finalizers or disabling the controller are gated behind explicit user confirmation.
When your agent uses it
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use for generic GKE cluster node pool creation or standard non-TPU workload management (use gke-basics or gke-cluster-creation instead).
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 (12 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-dynamic-slices-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-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring inside it instead.
Copy the skill folder to ~/.agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-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-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring inside it instead.
Copy the skill folder to ~/.cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-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-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/gke-ai-troubleshooting-tpu-dynamic-slices-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-dynamic-slices-monitoringOr copy the folder to ~/.gemini/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/gke-ai-troubleshooting-tpu-dynamic-slices-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-dynamic-slices-monitoring &&
cp -R "$tmp/skills/cloud/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring" ~/.copilot/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/gke-ai-troubleshooting-tpu-dynamic-slices-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-dynamic-slices-monitoring into your agent's skills folder as gke-ai-troubleshooting-tpu-dynamic-slices-monitoring. Agents that support SKILL.md read one folder per skill.
What it does
- Slice state analysis
- Reads slice status conditions and maps lifecycle states and reasons to likely causes and next actions.
- Provisioning failure checklist
- Verifies node existence, allocation, topology match and reservation block alignment when slices fail.
- Single-slice manifest validation
- Checks pod template annotations and node selectors needed to target a dynamic TPU slice.
- Multi-slice JobSet validation
- Confirms JobSet exclusive-topology annotation and TPU selectors for multi-slice workloads.
- Stuck finalizer removal
- Describes a guarded JSON patch to clear finalizers on slices stuck in deletion, with risk warnings.
- Slice controller teardown
- Outlines disabling the slice controller, removing the CRD and clearing TPU slice node labels.
Good for
- Check why a TPU slice is stuck in provisioning or shows a failed state
- Validate a single-slice TPU training pod manifest before deploying it
- Verify a multi-slice JobSet manifest targets TPU slices correctly
- Clean up a TPU slice stuck in deactivating after confirming the risks
- Disable GKE dynamic slicing on a cluster and remove leftover slice labels
Gke AI troubleshooting tpu dynamic slices monitoring FAQ
What tools does it need?
It needs kubectl and gcloud CLIs configured to access the GKE cluster, and Cloud Logging enabled for the project.
Does it change my cluster without asking?
No. Patching finalizers and disabling the slice controller are high-risk and require explicit user confirmation before execution.
When does it apply?
It applies to GKE TPU Dynamic Slices troubleshooting and manifest checks. It advises using gke-basics or gke-cluster-creation for general node pool creation or non-TPU workloads.
What license is it released under?
The skill is in the google/skills repository, which is licensed under Apache-2.0.
How do I install Gke AI troubleshooting tpu dynamic slices monitoring in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring to use it in all your projects, or to .claude/skills/gke-ai-troubleshooting-tpu-dynamic-slices-monitoring in one project.
Does Gke AI troubleshooting tpu dynamic slices 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 dynamic slices 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 dynamic slices monitoring?
The closest alternatives to Gke AI troubleshooting tpu dynamic slices monitoring are Gke AI troubleshooting tpu slice mig stuck updating, Gke AI troubleshooting tpu partition overlap, Aks GPU inference, Aks cost optimization and Gke AI troubleshooting tpu mxla hang.
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




