Agent skill · data analytics · google

gke-workload-troubleshooting

Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.

Why this skill is useful

Provides specific commands and workflows for diagnosing GKE workload failures that the AI wouldn't reliably generate on its own.

What it needs

Requires gcloud, kubectl installed locally. About 8k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

GKE Workload Troubleshooting Skill Use this skill to systematically diagnose and resolve failures in application workloads deployed in GKE clusters. This skill operates non-interactively and enforces a read-only diagnostics boundary: it only proposes fixes — whether Kubernetes manifest/config patches or Google Cloud changes (for example gcloud IAM bindings or node-pool recreation) — and never executes live mutations itself. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-workload-troubleshooting)" and append agent-skills/1.0 (skill:gke-workload-troubleshooting) to User-Agent headers. 🔍 Diagnostic Workflow Step 0: Non-Interactive Context Discovery & Time Window Definition 1. Parameter Extraction: Extract required context (projectid, clustername, clusterlocation, workloadname, workloadnamespace) non-interactively from the user prompt, active SETTINGS.md, or active environment defaults: Default workloadnamespace to default if omitted. Infer missing cluster parameters from active environment (kubectl config current-context or gcloud config get-value project). Prioritize non-interactive context discovery from prompts and environment defaults to ensure autonomous execution flow. 2. Cluster Credentials & Fallback Mode: Attempt credential fetch: gcloud container clusters get-credentials {clustername} --region/--zone {clusterlocation} Fallback / Dry-Run Mode: If the cluster is unreachable, non-existent, or live command execution fails (such as in sandboxed evaluations, dry-run mode, or offline analysis): Limit retry attempts to avoid resource exhaustion and context overflow in unreachable cluster scenarios. Immediately present the exact sequence of kubectl diagnostic commands for the human operator to run. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/gke-workload-troubleshooting

View the source on GitHub

Browse the @skills marketplace