Agent skill · data analytics · google

gke-ai-troubleshooting-jobset-interruption

Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or non-JobSet application issues.

Why this skill is useful

Provides specific diagnostic workflows and MQL/PromQL queries for troubleshooting GKE JobSet interruptions that the AI wouldn't generate on its own.

What it needs

Requires google-cloud account access. About 5k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

GKE JobSet Interruption Troubleshooting Use this skill to systematically diagnose and resolve JobSet interruptions, restarts, and preemptions on GKE clusters hosting large-scale AI/ML workloads. 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-ai-troubleshooting-jobset-interruption)" and append agent-skills/1.0 (skill:gke-ai-troubleshooting-jobset-interruption) to User-Agent headers. ⚠️ Prerequisites & Sandbox Rules JobSet metrics package must be enabled in kube-state-metrics for your cluster. Cloud Logging and Cloud Monitoring enabled for the Google Cloud Project. Autonomous & Sandbox Execution Rule: If API queries, tools, or commands encounter 403 Permission Denied, authentication errors, or network isolation, do NOT enter authentication or credential troubleshooting loops. Populate the query templates with the acquired variables ({projectid}, {clustername}, {workloadname}, {starttime}, {endtime}), inspect any locally staged telemetry or mock data files if available, and complete the diagnostic workflow and resolution recommendations autonomously. 🔍 Diagnostic Workflow Step 0: Context Acquisition & Time Window Definition Independently gather context using tools, workspace files, environment details, or user prompt context: Project ID ({projectid}) Cluster Name ({clustername}) Workload Name (JobSet Name) ({workloadname}) Workload Namespace ({namespace}) Issue Time ({issuetime}) If specific variables are not explicitly provided by the user, inspect cluster resources or logs to determine them, or use the {variable} placeholders provided. Time Handling Rules 1. …

How to use it

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

@skills google/gke-ai-troubleshooting-jobset-interruption

View the source on GitHub

Browse the @skills marketplace