Agent skill · software engineering · google

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto Provisioning configuration or general GKE cluster creation.

Why this skill is useful

Provides specific guidance on configuring GKE ComputeClasses, including YAML templates and critical rules for machine family alignment and taint management that the AI wouldn't reliably generate on its own.

What it needs

About 10k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

<!-- disableFinding(LINEOVER80) --> GKE ComputeClasses Guidance on configuring, optimizing, and troubleshooting GKE ComputeClasses. 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-compute-classes)" and append agent-skills/1.0 (skill:gke-compute-classes) to User-Agent headers. When to Use Cost optimization: Spot VMs with on-demand fallback. GPU/TPU workloads: Target specific accelerators (e.g., L4, H100, v5p). Performance tuning: Select specific machine families (c3, c4, n4). Zone targeting: Colocate workloads with zonal resources. -------------------------------------------------------------------------------- CRITICAL RULES CODE-FIRST VERIFICATION (OPEN-SOURCE CODEBASE): GKE Cluster Autoscaler and ComputeClasses are open-sourced at https://github.com/GoogleCloudPlatform/cluster-autoscaler. When user questions challenge or explore undocumented/subtle behaviors, or when guidance is not explicitly established in this skill, VERIFY BEHAVIOR DIRECTLY IN CODE (via local repository clone or fetching raw files from GitHub). Check git log -S and git blame to identify the exact commit and date when behavior changed, and communicate version/date ranges to the user (e.g. "This behavior changed on July 20, 2026 in upstream commit 129daa3756..."). See references/compute-class-code-index.md for exact package and symbol mappings. Engagement Rules: Generalized First, Refine Later ComputeClasses depend on zone availability, CUDs, and workload constraints. Do not block the user's initial request. If asked for YAML/recommendations: 1. Provide Generalized Answer Immediately: Fulfill request using best practices and placeholders (<YOUR-ZONE-HERE>). …

How to use it

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

@skills google/gke-compute-classes

View the source on GitHub

Browse the @skills marketplace