本文へ移動
cccskills
無料GitHub で公開

google-cloud-waf-operational-excellence

Generates operations-focused guidance for Google Cloud workloads based on the design principles and recommendations in the Operational Excellence pillar of the Google Cloud Well-Architected Framework (WAF). Use this skill to evaluate a workload, identify operational requirements, and provide actionable recommendations for deployment, monitoring, and incident management.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Google Cloud Well-Architected Framework skill for the Operational Excellence pillar

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:

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 resources and right-sizing opportunities.
    • 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.
  • 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 before production deployment.
    • Service Level Objectives (SLOs) are explicitly defined and monitored using automated tools.
  • Incident management

    • Incident response roles and communication channels are clearly defined and documented.
    • A structured, blameless post-mortem process is followed for all major incidents.
  • Change automation

    • All infrastructure changes are performed using Infrastructure as Code (IaC) to ensure consistency.
    • CI/CD pipelines are integrated with automated testing for all deployment changes.
  • Resource optimization

    • Resource utilization is regularly reviewed using recommendations from Active Assist or performance data.
  • Culture of improvement

    • A documented strategy is in place for regularly reviewing and adapting cloud operations to industry advancements.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

tensology のスキルをすべて見る

このスキルの問題を報告する