/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,
Claude Code
$ npx -y skills add google/skills --skill google-cloud-waf-cost-optimization --agent claude-code
Codex
$ npx skills add google/skills --skill google-cloud-waf-cost-optimization -a codex -y
Cursor
$ npx skills add google/skills --skill google-cloud-waf-cost-optimization -a cursor -y
Gemini CLI
$ npx skills add google/skills --skill google-cloud-waf-cost-optimization -a gemini-cli -y
GitHub Copilot
$ npx skills add google/skills --skill google-cloud-waf-cost-optimization -a github-copilot -y
OpenCode
$ npx skills add google/skills --skill google-cloud-waf-cost-optimization -a opencode -y
Windsurf
$ npx skills add google/skills --skill google-cloud-waf-cost-optimization -a windsurf -y
SKILL.md
google-cloud-waf-cost-optimization.SKILL.mdname: google-cloud-waf-cost-optimization
metadata:
version: "1.0.2"
category: WellArchitectedFramework
description: 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.
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](references/attribution.md).
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.
Core principles
The recommendations in the cost optimization pillar of the Well-Architected Framework are aligned with the following core principles:
- **Align cloud spending with business value**: Ensure that your cloud
resources deliver measurable business value by aligning IT spending with business objectives. Prioritize investments that directly contribute to revenue, customer satisfaction, or operational efficiency. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/align-cloud-spending-business-value.md.txt
- **Foster a culture of cost awareness**: Ensure that people across your
organization consider the cost impact of their decisions and activities. Provide teams with the visibility and information they need to make informed, cost-conscious choices. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/foster-culture-cost-awareness.md.txt
- **Optimize resource usage**: Provision only the resources that you need and
pay only for what you consume. Select the most cost-effective resource types, sizes, and locations that meet your technical and business requirements. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-resource-usage.md.txt
- **Optimize continuously**: Continuously monitor your cloud resource usage and
costs, and proactively make adjustments as needed to optimize your spending. This iterative approach helps identify and address inefficiencies before they become significant. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-continuously.md.txt
Relevant Google Cloud products
The following are _examples_ of Google Cloud products and features that are relevant to cost optimization:
- **Visibility and monitoring**:
- **Cloud Billing reports**: Built-in dashboards for visualizing spending and
trends. **Essential for visibility within the console.**
- **BigQuery billing export**: Enables granular, custom analysis of billing
data using SQL and BI tools.
- **Looker Studio**: Used for creating detailed, shared cost dashboards and
reports. **Use alongside Cloud Billing reports for custom visual insights.**
- **Billing alerts and budgets**: Automated notifications when spending
reaches predefined thresholds.
- **Storage Insights**: Used to analyze Cloud Storage access patterns and identify
cost-saving opportunities.
- **Automation and optimization tools**:
- **Recommender / Active Assist**: Automatically identifies idle resources,
rightsizing opportunities, and unused commitments.
- **Cloud Hub Optimization**: Integrates billing and resource utilization data
to help developers and application owners quickly identify their most expensive, fluctuating, or underutilized cloud resources.
- **FinOps hub**: Presents active savings and optimization opportunities in
one dashboard.
- **Billing quotas**: Limits on resource consumption to prevent unexpected
cost spikes.
- **Efficient infrastructure**:
- **Managed services and serverless services**: Services like Cloud Run, Cloud
Run functions, and GKE Autopilot reduce operational overhead and pay-per-use scaling.
- **Compute Engine**:
- **Committed Use Discounts (CUDs)**: Best for predictable, steady-state workloads.
- **Spot VMs**: Best for fault-tolerant, interruptible, or unpredictable batch tasks.
- **Sustained Use D
Read more
name: google-cloud-waf-cost-optimization metadata: version: "1.0.2" category: WellArchitectedFramework description: 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.
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](references/attribution.md).
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.
Core principles
The recommendations in the cost optimization pillar of the Well-Architected Framework are aligned with the following core principles:
- **Align cloud spending with business value**: Ensure that your cloud
resources deliver measurable business value by aligning IT spending with business objectives. Prioritize investments that directly contribute to revenue, customer satisfaction, or operational efficiency. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/align-cloud-spending-business-value.md.txt
- **Foster a culture of cost awareness**: Ensure that people across your
organization consider the cost impact of their decisions and activities. Provide teams with the visibility and information they need to make informed, cost-conscious choices. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/foster-culture-cost-awareness.md.txt
- **Optimize resource usage**: Provision only the resources that you need and
pay only for what you consume. Select the most cost-effective resource types, sizes, and locations that meet your technical and business requirements. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-resource-usage.md.txt
- **Optimize continuously**: Continuously monitor your cloud resource usage and
costs, and proactively make adjustments as needed to optimize your spending. This iterative approach helps identify and address inefficiencies before they become significant. Grounding document: https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-continuously.md.txt
Relevant Google Cloud products
The following are _examples_ of Google Cloud products and features that are relevant to cost optimization:
- **Visibility and monitoring**:
- **Cloud Billing reports**: Built-in dashboards for visualizing spending and
trends. **Essential for visibility within the console.**
- **BigQuery billing export**: Enables granular, custom analysis of billing
data using SQL and BI tools.
- **Looker Studio**: Used for creating detailed, shared cost dashboards and
reports. **Use alongside Cloud Billing reports for custom visual insights.**
- **Billing alerts and budgets**: Automated notifications when spending
reaches predefined thresholds.
- **Storage Insights**: Used to analyze Cloud Storage access patterns and identify
cost-saving opportunities.
- **Automation and optimization tools**:
- **Recommender / Active Assist**: Automatically identifies idle resources,
rightsizing opportunities, and unused commitments.
- **Cloud Hub Optimization**: Integrates billing and resource utilization data
to help developers and application owners quickly identify their most expensive, fluctuating, or underutilized cloud resources.
- **FinOps hub**: Presents active savings and optimization opportunities in
one dashboard.
- **Billing quotas**: Limits on resource consumption to prevent unexpected
cost spikes.
- **Efficient infrastructure**:
- **Managed services and serverless services**: Services like Cloud Run, Cloud
Run functions, and GKE Autopilot reduce operational overhead and pay-per-use scaling.
- **Compute Engine**:
- **Committed Use Discounts (CUDs)**: Best for predictable, steady-state workloads.
- **Spot VMs**: Best for fault-tolerant, interruptible, or unpredictable batch tasks.
- **Sustained Use D
This repository contains Agent Skills for Google products and technologies, including Google Cloud.
Other skills on skills.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about google-cloud-waf-cost-optimization.
- Which coding agents can use google-cloud-waf-cost-optimization?
- google-cloud-waf-cost-optimization installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

