Google Cloud Waf Operational Excellence
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 structured recommendations and best practices for managing cloud operations on Google Cloud. It aligns with the Operational Excellence pillar of the Google Cloud Well-Architected Framework, covering areas such as operational readiness, incident management, resource optimization, change automation, and continuous improvement. The skill includes assessment questions to help identify operational gaps and a validation checklist to ensure workloads meet established standards for efficiency, reliability, and performance.
What it does
- Provides best practices for operational readiness and performance measurement.
- Offers guidance on establishing incident response and post-incident review processes.
- Recommends strategies for resource right-sizing and capacity management.
- Outlines approaches for automating infrastructure changes and CI/CD pipelines.
- Includes a validation checklist for evaluating architectural alignment with operational standards.
- Suggests relevant Google Cloud products for monitoring, automation, and resource management.
When to use it
- When designing or reviewing cloud architecture for operational efficiency.
- When establishing processes for incident management and root cause analysis.
- When planning to implement or improve CI/CD and infrastructure-as-code practices.
- When assessing the operational readiness of a workload before production deployment.
- When looking to optimize resource utilization and reduce technical debt.
Advantages
- Aligns operational practices with official Google Cloud architectural standards.
- Promotes a culture of continuous improvement and blameless learning.
- Helps identify specific gaps in operational processes through targeted assessment questions.
- Provides actionable checklists to verify workload health and readiness.
Usage examples
- “How can I improve my incident management process for Google Cloud workloads?”
- The agent will provide a structured approach to incident response, including defining roles like Incident Commander, setting up communication channels, and implementing a blameless post-incident review process.
- “What are the best practices for automating infrastructure changes on Google Cloud?”
- The agent will outline the use of Infrastructure as Code (IaC) with tools like Terraform and suggest integrating CI/CD pipelines using Cloud Build and Cloud Deploy for consistent, low-risk deployments.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-waf-operational-excellence/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-waf-operational-excellence.zip -d .agents/skills
Documentation by Google
Google Cloud Well-Architected Framework skill for the Operational Excellence 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 operational excellence pillar in the Google Cloud Well-Architected Framework provides recommendations to operate workloads efficiently on Google Cloud. Operational excellence in the cloud involves designing, implementing, and managing cloud solutions that provide value, performance, security, and reliability. The recommendations in this pillar help you to continuously improve and adapt workloads to meet the dynamic and ever-evolving needs in the cloud.
Core principles
The recommendations in the operational excellence pillar of the Well-Architected Framework are aligned with the following core principles:
Ensure operational readiness: Define and measure criteria for a workload to be considered ready for production across staffing, processes, tools, and governance. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/operational-readiness-and-performance-using-cloudops.md.txt
Manage incidents and problems: Establish structured processes for incident response, communication, and root cause analysis to minimize impact and prevent recurrence. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-incidents-and-problems.md.txt
Manage and optimize cloud resources: Monitor resource utilization and right-size environments to maintain performance while ensuring operational efficiency. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-and-optimize-cloud-resources.md.txt
Automate and manage change: Use Infrastructure as Code (IaC) and CI/CD pipelines to ensure consistent, repeatable, and low-risk deployments and configuration changes. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/automate-and-manage-change.md.txt
Continuously improve and innovate: Adopt a flexible and agile approach to cloud operations, foster a culture of continuous improvement, and periodically review your cloud architecture against current business goals, technological advancements, and industry trends. Grounding document: https://docs.cloud.google.com/architecture/framework/operational-excellence/continuously-improve-and-innovate.md.txt
Relevant Google Cloud products
The following are examples of Google Cloud products and features that are relevant to operational excellence:
Observability and monitoring
Cloud Monitoring: Full-stack observability for Google Cloud and hybrid environments.
Cloud Logging: Real-time log management and analysis at scale.
Error Reporting: Aggregates and displays errors for running cloud services.
Service Monitoring: Tools for defining and tracking Service Level Objectives (SLOs).
Automation and CI/CD
Cloud Build: Serverless platform for building, testing, and deploying software.
Cloud Deploy: Managed continuous delivery service for GKE, Cloud Run, and GCE.
Terraform / Infrastructure Manager: Managed service for Infrastructure as Code (IaC) automation.
Artifact Registry: Central repository for managing build artifacts and container images.
Resource management and optimization
Recommender (Active Assist): Automatically identifies idle or over-provisioned resources and right-sizing opportunities.
Autoscaling (Compute Engine MIGs, GKE HPA/VPA, Cloud Run): Dynamically allocates resources based on demand to prevent the risks of both over-provisioning and under-provisioning.
Resource Manager: Hierarchical management of resources across organizations, folders, and projects.
Incident response
Incident response & management (IRM): Structured tools and processes for managing operational disruptions.
Workload assessment questions
Ask appropriate questions to understand operations-related requirements and constraints of the workload and the user's organization. Choose questions from the following list:
Operational readiness and performance
How do you define and measure operational readiness for your cloud workloads and what specific criteria or metrics do you use?
Describe your process for defining, tracking, and achieving SLOs for your critical workloads.
How do you ensure that your workloads can seamlessly leverage multiple machine types or families for VMs during capacity constraints?
What is your strategy for modernizing your cloud resources to avoid technical debt and availability risks?
Incident and problem management
Describe your incident management process, including roles, responsibilities, and communication channels.
How do you conduct post-incident reviews (PIRs) to identify root causes and implement preventive measures?
Resource management and optimization
How do you ensure that your cloud resources are right-sized for your workloads, and what tools or techniques do you use?
Change automation
Describe your change management process, including approval workflows, testing procedures, and deployment strategies.
How do you automate deployments, ensure their consistency and manage configuration?
Continuous improvement
How do you ensure that your cloud operations are continuously adapting to meet evolving business needs and technological advancements?
Validation checklist
Use the following checklist to evaluate the architecture's alignment with operational excellence recommendations:
Operational readiness
[ ] A formal framework or set of criteria exists to assess operational readiness across staffing, processes, tooling, and governance before deployment to production.
[ ] Service Level Indicators (SLIs) based on user journeys, Service Level Objectives (SLOs), and error budgets are explicitly defined and monitored using Cloud Monitoring.
[ ] Workloads achieve continuous availability by using automated spillover mapping (via Managed Instance Groups (Flexible MIGs) with mixed-instance templates or GKE Custom Compute Classes) to seamlessly utilize cross-generation machine types across multiple zones in a region.
[ ] Workloads follow a "Migration-by-Design" strategy that leverages instance flexibility and automated spillover mapping to naturally transition workloads to newer hardware generations (evergreen capacity), decouple workloads from rigid, specific machine types to avoid capacity constraints, and align deployments with Google Cloud's most obtainable physical fleet to minimize availability risks.
Incident management
[ ] Incident response roles (such as an Incident Commander), communication channels, escalation paths, and automated response tasks are clearly defined and documented.
[ ] A structured, blameless post-incident review (PIR) process is followed for all major incidents to conduct thorough root cause analysis and implement preventive measures.
Change automation
[ ] All infrastructure changes are performed using Infrastructure as Code (IaC) stored in version control (using modern tools like Terraform) to ensure consistency and enable automated deployments.
[ ] CI/CD pipelines (using Cloud Build for continuous integration and Cloud Deploy for continuous delivery) are integrated with automated testing for all deployment changes.
Resource optimization
[ ] Resource utilization is regularly reviewed, and resources are right-sized using Recommender (Active Assist) and autoscaling to mitigate the risks of over-provisioning and under-provisioning.
Culture of improvement
[ ] The organization uses agile operational practices, iterative workflows, and adaptable operating models.
[ ] Leadership fosters a culture of continuous improvement, psychological safety, and ongoing learning.
[ ] Teams periodically review their cloud architecture against business goals, industry trends, and technological advancements.
Files
- ATTRIBUTION.mdAdded by AutoGineer896 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md9.4 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.
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-operational-excellence · 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-operational-excellence.zip