Agent skill · data analytics · google

google-cloud-waf-cost-optimization

Evaluates Google Cloud workloads for cost efficiency and FinOps alignment using the Google Cloud Well-Architected Framework Cost Optimization pillar. Use when the user asks to analyze Google Cloud spend, reduce cloud bills, rightsize resources (for example, Compute, GKE, Storage, Databases), evaluate discount options (for example, CUDs, SUDs, Spot VMs), or eliminate idle capacity. Do not use for standalone product pricing lookups or non-cost architecture design.

Why this skill is useful

Provides actionable recommendations for optimizing costs in Google Cloud workloads that the AI wouldn't reliably 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

Google Cloud Well-Architected Framework skill for the Cost Optimization pillar Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Overview The Cost Optimization pillar of the Google Cloud Well-Architected Framework provides a structured approach to optimize the costs of your cloud workloads while maximizing business value. Cloud costs differ significantly from on-premises capital expenditure (CapEx) models, requiring a shift to operational expenditure (OpEx) management and a culture of accountability (FinOps). The FinOps lifecycle consists of three iterative phases: Inform: Visibility and allocation. Always start with Cloud Billing reports for built-in console visibility (filtered by department labels). Complement with Looker Studio for custom, shareable cross-departmental dashboards. Optimize: Rates and usage. Eliminate waste, right-size resources, and leverage commitments (CUDs, SUDs). Operate: Continuous improvement. Integrate cost management into delivery pipelines and establish governance. Operational instructions Comprehensive First: Always provide a complete list of standard recommendations/strategies relevant to the service or scenario mentioned. Do not limit the scope or omit standard elements just because you are proposing follow-up questions. Full Conjunction: When an instruction bundles multiple actions (e.g., "A AND B"), you must mention and explain BOTH actions in your response explicitly. Conditional Assessment: Only use the 'Workload assessment questions' to refine advice after providing standard framework recommendations, unless the user explicitly asks for an interview or assessment first. …

How to use it

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

@skills google/google-cloud-waf-cost-optimization

View the source on GitHub

Browse the @skills marketplace