gcp-resource-optimizer

Optimize Google Cloud resource allocation, costs, and expiring credit usage.

Updated May 16, 2026
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill gcp-resource-optimizer-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gcp-resource-optimizer
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/gcp-resource-optimizer
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill gcp-resource-optimizer-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cloud bills grow silently through oversized VMs, idle disks, wrong storage classes, and unplanned credit expiration. This Skill provides concrete gcloud commands, BigQuery billing queries, and architecture patterns to reduce GCP spend and extract maximum value from credits before they expire. ## Core Features & Use Cases - Credit Burn Planning: Calculate required daily spend from expiring credits and prioritize lasting-value workloads like model training and dataset generation over ephemeral compute. - Cost Optimization Patterns: Right-size Compute Engine instances, configure Cloud Run scale-to-zero, apply Cloud Storage lifecycle rules, and control BigQuery bytes billed. - Billing Analysis: Ready-to-run BigQuery queries for cost by service, SKU, project, and label, plus anomaly detection and credit burn forecasting. - Use Case: You have $5,000 in GCP credits expiring in 45 days. Use this Skill to compute the required daily burn rate, identify high-value workloads to run, and set budget alerts at 50%, 90%, and 100% thresholds. ## Quick Start Ask the assistant to analyze your GCP project's current spend and recommend right-sized instances and storage classes to reduce next month's bill.

Frequently Asked Questions about gcp-resource-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce GCP Compute Engine costs?▼

Use the MachineTypeRecommender via gcloud recommender to find oversized instances, switch to e2 machine types for general workloads, and use Spot VMs for fault-tolerant batch jobs at 60-91% discounts. Committed use discounts save 37% for 1-year and 55% for 3-year terms.

How to analyze GCP billing data with BigQuery?▼

Enable billing export to BigQuery under Billing settings, then query the gcp_billing_export_v1 tables. The Skill provides queries for daily spend, cost by service, SKU, project, and label, plus day-over-day anomaly detection using 7-day rolling averages.

What should I spend expiring GCP credits on?▼

Prioritize workloads with lasting value: ML model training, container image builds, dataset generation, and batch processing of accumulated work. Avoid burning credits on ephemeral compute like dev VMs that leave no persistent artifact.

When should I use Spot VMs versus standard instances?▼

Use Spot VMs for batch jobs, fault-tolerant workloads, and development environments where 30-second termination notice is acceptable, saving 60-91%. Avoid them for production services and stateful workloads that cannot tolerate preemption.

How do I find unused GCP resources to delete?▼

Run gcloud compute disks list with a NOT users:* filter for unattached disks, gcloud compute addresses list with status=RESERVED for unused static IPs, and filter snapshots by creationTimestamp for old backups. Review the list before deleting anything.

Does Cloud Run scale to zero to save costs?▼

Yes, set the autoscaling.knative.dev/minScale annotation to 0 so idle services incur no compute charges. Combine with containerConcurrency of 80, CPU throttling enabled, and a maxScale cap to control costs under load.