Skip to main content
Agent skill

Gke Cost Analysis

Answer natural language questions and perform analysis on GKE cluster and workload costs using BigQuery billing exports, cost allocation data, and live cluster monitoring metrics. Use when querying GKE costs across projects, namespaces, or workloads, analyzing billing reports in BigQuery (bq), checking cluster cost budgets (gcloud billing), or diagnosing cost drivers like pod requests vs. actual utilization (kubectl top). Don't use for applying cost optimization changes, creating rightsizing manifests (VPA/MPA), or selecting ComputeClasses (use gke-cost-optimization instead).

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Gke Cost Analysis when an AI agent needs a reusable SKILL.md workflow for this job: Answer natural language questions and perform analysis on GKE cluster and workload costs using BigQuery billing exports, cost allocation data, and live cluster monitoring metrics. Use when querying GKE costs across projects, namespaces, or workloads, analyzing billing reports in BigQuery (bq), checking cluster cost budgets (gcloud billing), or diagnosing cost drivers like pod requests vs. actual utilization (kubectl top). Don't use for applying cost optimization changes, creating rightsizing manifests (VPA/MPA), or selecting ComputeClasses (use gke-cost-optimization instead).

When not to use it

Skip Gke Cost Analysis when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/gke-cost-analysis
# Save SKILL.md to ~/.claude/skills/gke-cost-analysis/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/gke-cost-analysis/SKILL.md. For a shared project, commit the folder at .claude/skills/gke-cost-analysis/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Gke Cost Analysis skill for this task: Use Gke Cost Analysis when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# GKE Cost Analysis

This skill provides guidance on answering natural language questions about GKE-related costs, billing reports, and utilization analysis.

## Attribution

**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you MUST read [Usage Attribution](references/attribution.md). For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix `gcloud` with `CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:gke-cost-analysis)"` and append `agent-skills/1.0 (skill:gke-cost-analysis)` to `User-Agent` headers.

## Overview

When users ask about GKE costs (e.g., "What are my costs across projects?", "What's my most expensive namespace?", "Why is my cluster cost spiking?"), use this skill to provide a structured and expert response using BigQuery billing exports, cost allocation metadata, and live cluster metrics.

## Instructions

When handling a cost-related question:

1. **Provide a Direct Answer**: Address the specific cost question or analytical request clearly and concisely. 2. **Explain BigQuery Integration**: Explain how to query BigQuery for historical cost breakdown. Note that GKE costs originate from the GCP Billing Detailed BigQuery Export (`gcp_billing_export_resource_v1_*`). 3. **Check & Verify Cost Allocation**: Explain that GKE Cost Allocation must be enabled on the cluster (`--enable-cost-allocation`) for namespace, label, and workload-level billing granularity. If queries return empty labels, provide the `gcloud` command to enable it. 4. **Analyze Pricing Drivers & Utilization**: When diagnosing cost drivers, explain whether the cluster is in Autopilot (billed by requested pod CPU/memory) or Standard mode (billed by underlying VM node size + control plane fees), and compare live utilization (`kubectl top`) against provisioned requests. 5. **Provide Actionable Commands/Queries**: Provide concrete BigQuery CLI (`bq query`) commands or read-only `gcloud`/`kubectl` inspection commands. Prefer `bq` over BigQuery Studio when available.

## Key Points & Pricing Drivers

- **Data Source**: GKE costs come from GCP Billing Detailed BigQuery Export. The user must provide the full path to their BigQuery table (dataset name and table name containing the Billing Account ID). - **Granularity Requirement**: GKE Cost Allocation (`--enable-cost-allocation`) must be enabled on the cluster to populate `goog-k8s-cluster-name`, `k8s-namespace`, `k8s-workload-name`, and `k8s-workload-type` labels in BigQuery. - **Autopilot vs. Standard Cost Drivers**: - **Autopilot Pricing**: Billed directly on pod resource requests (`requests.cpu`, `requests.memory`, ephemeral storage). Over-requested pods drive up billing regardless of whether the pod actively uses those CPU cycles or memory. - **Standard Pricing**: Billed on provisioned node pool VMs (`e2`, `n4`, `c3`, etc.). Idle nodes or multiple low-utilization dev clusters drive excess infrastructure costs. - **Cluster Management Fee**: ~$0.10/hour per cluster applies to BOTH Standard and Autopilot modes. The free tier waives it for one eligible cluster per billing account. - **Credits & Discounts Impact**: When analyzing `cost` versus `cost_before_credits`, note that Committed Use Discounts (CUDs) and Spot VMs appear as credits or reduced rate charges in the billing export. - **Tools & Syntax**: BigQuery CLI (`bq`) is preferred. When writing Standard SQL queries, use a dot (`.`) instead of a colon (`:`) to separate the project ID and dataset name (`{project_id}.{dataset_name}.{table_name}`). - **Defaults**: Assume last 30 days, row limit 10, ordering by cost descending (`ORDER BY cost DESC`), unless specified otherwise.

## Live Cluster & Cost Monitoring

Use read-only CLI commands to inspect current cluster budgets, node utilization, and pod resource consumption vs. requests:

```bash # View billing budgets for an account (requires Cost Management API) gcloud billing budgets list --billing-account={billing_account} --quiet

# View live node resource utilization across the cluster kubectl top nodes

# View pod resource usage across namespaces (compare against requested limits to diagnose waste) kubectl top pods --all-namespaces --containers ```

> **Warning — cluster mutation, not read-only:** Enabling GKE cost allocation > modifies the cluster. Get explicit user confirmation before running it, and > note that namespace/workload labels populate in the billing export only from > enablement onward (no historical backfill). > > ```bash > gcloud container clusters update {cluster_name} \ > --enable-cost-allocation \ > --region {region} > ```

## Applying Cost Optimizations

To apply rightsizing changes based on analysis (such as setting up `VPA` recommendation mode, adjusting CPU/memory to `P95 * 1.2`, configuring Spot VMs via `nodeSelector` or `ComputeClass`, enforcing `ResourceQuotas`, or selecting machine types and CUDs), use the **`gke-cost-optimization`** skill.

## BigQuery Query Templates

Ready-to-adapt `bq query` templates — single workload cost, per-workload per-cluster breakdown, per-namespace breakdown — with the placeholder policy and defaults (30 days, `LIMIT 10`, `ORDER BY cost DESC`) are in [references/billing-queries.md](references/billing-queries.md). All parameters (dataset, table, project, cluster, etc.) must be replaced with user values.

Note: Checking that the `goog-k8s-cluster-name` label exists scopes the total billing data specifically to GKE costs.

Intended uses

  • Use Gke Cost Analysis when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.