Agent skill · software engineering · google

gke-productionize

Orchestrates comprehensive production readiness reviews and assessments for GKE clusters and workloads across scalability, security, reliability, observability, backup/DR, and cost optimization. Use when asked to productionize, prepare, assess, audit, or review a GKE cluster or workload before going live to production. Don't use for deep-dive single-domain implementation (use specific domain skills like gke-workload-scaling, gke-platform-security, gke-workload-security, gke-service-networking, gke-reliability instead).

Why this skill is useful

Adds specific commands and workflows for assessing GKE clusters and workloads that the AI wouldn't reliably generate on its own.

What it needs

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

What this skill does

GKE Productionize Skill This skill acts as a high-level orchestrator for preparing a GKE cluster and its workloads for production readiness. [!IMPORTANT] This is a meta-skill or orchestrator skill. You are expected to invoke and run many other specialized skills listed in this document as part of the overall productionization process. Do not attempt to implement all production readiness features directly within this skill; instead, use this skill to assess the environment and then delegate to the specific skills for each domain. 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-productionize)" and append agent-skills/1.0 (skill:gke-productionize) to User-Agent headers. Scope This skill is adaptable to: A single application (already on Kubernetes or not). A set of applications. A target cluster. Workflow 1. Discovery Phase Before making recommendations, discover the current state of the environment. Cluster Discovery Run these commands to understand the cluster setup: Check cluster details: gcloud container clusters describe {clustername} --location {location} --project {project} Check for Autopilot vs Standard: Look for the following block in the describe output: Check release channel: Look for releaseChannel. Workload Discovery If a specific application is targeted, discover its configuration: Get deployment/statefulset details: kubectl get deployment {appname} -n {namespace} -o yaml Check for dedicated namespace and labels: kubectl get namespace {namespace} -o yaml (Look for Pod Security Standards labels). Check for dedicated service account usage: kubectl get pods -n {namespace} -o custom-columns="NAME:.metadata.name,SERVICEACCOUNT:.spec.serviceAccountName" Check for resource requests and limits. …

How to use it

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

@skills google/gke-productionize

View the source on GitHub

Browse the @skills marketplace