Google Cloud Waf Cost Optimization
GoogleOfficialPublished by Google
- Skill
- Guidelines
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to managing and reducing Google Cloud costs by applying the Cost Optimization pillar of the Google Cloud Well-Architected Framework. It emphasizes the FinOps lifecycle—Inform, Optimize, and Operate—to help organizations move from reactive spending to proactive, value-driven cloud financial management. The skill covers visibility tools, resource rightsizing, commitment strategies like CUDs and SUDs, and governance practices to ensure sustainable cloud efficiency.
What it does
- Provides strategies for visibility using Cloud Billing reports and Looker Studio.
- Identifies opportunities for rightsizing compute, storage, and database resources.
- Explains how to leverage discount models including CUDs, SUDs, and Spot VMs.
- Offers guidance on implementing lifecycle policies for storage cost management.
- Suggests network optimization techniques like using Standard Network Tiers and Cloud CDN.
- Includes a validation checklist for auditing existing cloud architectures.
When to use it
- When analyzing current Google Cloud spend to identify waste.
- When planning to rightsize infrastructure for better cost efficiency.
- When evaluating commitment options like CUDs versus passive SUDs.
- When establishing a culture of cost awareness and FinOps governance.
- When auditing an architecture against Well-Architected Framework standards.
Advantages
- Aligns cloud spending directly with measurable business value.
- Promotes continuous improvement through iterative FinOps cycles.
- Provides actionable, framework-aligned recommendations for diverse Google Cloud services.
- Helps balance technical performance requirements with cost constraints.
Usage examples
- “How can I reduce my monthly Google Cloud compute bill?”
- The agent will provide a strategy covering rightsizing via Active Assist, evaluating CUDs and SUDs, and identifying idle resources.
- “What are the best practices for managing storage costs in Cloud Storage?”
- The agent will recommend using Storage Insights to analyze access patterns before implementing lifecycle policies to move data to lower-cost tiers.
- “How do I improve cost visibility across my organization's projects?”
- The agent will suggest using labels for attribution, setting up BigQuery billing exports, and creating custom dashboards in Looker Studio.
- “Audit my current architecture for cost optimization.”
- The agent will walk through the validation checklist, asking about labeling, budget alerts, and resource utilization to identify gaps.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-waf-cost-optimization/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-waf-cost-optimization.zip -d .agents/skills
Documentation by Google
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.
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 Discounts (SUDs): Passive, automatic discounts for instances running a significant portion of the month without commitments. Always mention this as a passive alternative or complement to CUDs.
Cloud Storage Lifecycle Policies: Automated moves data to lower-cost storage classes (Nearline, Coldline, Archive) based on age or access. Note: Always recommend Storage Insights first to understand current access patterns before defining lifecycle rules.
Networking and Content Delivery:
Location awareness: Keep traffic within a single region where possible to avoid inter-region data transfer costs.
Cloud CDN: Caches content to reduce data egress from the origin.
Network Service Tiers: Offers Standard Tier as a lower-cost option compared to Premium Tier for latency-tolerant traffic.
Cloud Interconnect / Direct Peering: Optimizes costs for high-volume data transfer to on-premises environments. Note: Always clarify hybrid connectivity options when discussing egress control, as on-premises sync is often a factor in multi-regional designs.
Managed Databases:
Instance sizing: Right-size CPU and memory based on Cloud Monitoring metrics.
High Availability (HA): Implement HA only for production environments to avoid doubling node costs for all environments.
Storage Optimization: Optimize storage costs by managing backup retention policies AND explicitly identifying and deleting unused or idle resources (like unused and orphaned disks, expired snapshots, or idle instances).
Organization and governance:
Resource Manager: Logical structure (Organizations, Folders, Projects) for cost attribution.
Labels: Metadata tags for categorizing and filtering costs by environment, team, or application.
Organization Policy Service: Enforces constraints (e.g., restricted regions or machine types) to control costs.
Workload assessment questions
Ask appropriate questions to understand the cost-related requirements and constraints of the workload and the user's organization. Choose questions from the following list:
How do you incorporate cost considerations into your cloud architecture design process?
How do you foster a culture of cost awareness among your development teams?
How do you monitor and manage cloud costs across different projects or departments?
What strategies do you use to optimize the cost of your compute resources?
How do you balance cost optimization with the need for agility and innovation?
How do you ensure that you are not over-provisioning cloud resources?
How do you use data and analytics to drive cost optimization decisions?
How do you optimize costs in different environments (e.g., development, testing, production)?
How do you ensure that your cost optimization efforts are sustainable and ongoing?
How do you measure the success of your cloud cost optimization initiatives?
Validation checklist
Use the following checklist to evaluate the architecture's alignment with cost-optimization recommendations:
Cost Attribution: 100% of resources are labeled with key metadata (e.g.,
env,team,app).Granular Visibility: BigQuery billing export is enabled and used for regular cost reviews.
Budgets and Alerts: Every project or business unit has defined budgets and active alerts.
Rightsizing: Resources are regularly adjusted based on rightsizing suggestions provided by Active Assist Recommender.
Commitment Strategy: Spend is reviewed monthly to optimize Committed Use Discount (CUD) coverage. For non-committed workloads, verify if Sustained Use Discounts (SUDs) are being captured automatically.
Idle Resource Management: Unused disks, IP addresses, and idle VMs are identified and removed monthly.
Managed Services: Serverless options are preferred for new workloads unless specific technical constraints exist.
Storage Tiers: Lifecycle policies are active for all major storage buckets to minimize archival costs. Be aware of retrieval fees associated with Nearline, Coldline and Archive storage classes.
Network Egress: Data transfer is minimized by keeping traffic regional, using Cloud CDN, and leveraging Standard Network Tier where appropriate. High-volume on-premises traffic uses Direct Peering or Cloud Interconnect (always verify if hybrid connectivity is involved).
Native Reporting: Cloud Billing reports must be used for standard views of spending trends in the console.
Custom Dashboards: Looker Studio is used for advanced, shareable, and customized reporting.
Files
- ATTRIBUTION.mdAdded by AutoGineer886 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md10.5 KiB
- references/attribution.md1.9 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/google-cloud-waf-cost-optimization · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google or Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-waf-cost-optimization.zip