AGENT SKILL

google-cloud-waf-reliability

Evaluates, designs, and improves the reliability, resilience, availability, fault tolerance, and disaster recovery (DR) of Google Cloud workloads based on the design principles and recommendations in the Reliability pillar of the Google Cloud Well-Architected Framework. Use when the user asks about reliability-related topics like workload uptime, designing for high availability (HA) or DR, setting and meeting RTO/RPO targets, SRE best practices, backup strategies, multi-region failover, or fault-tolerant architecture on Google Cloud. Don't use for other Well-Architected Framework pillars such as Cost Optimization, Operational Excellence, or Security, or for hands-on resource deployment and live incident troubleshooting.

License 许可
Apache-2.0
最近更新
2026-11-11
Stars
★ 2
Forks
0

01 前言 Front Matter

name
google-cloud-waf-reliability
metadata
{ "version": "1.0.2", "category": "WellArchitectedFramework" }
description
Evaluates, designs, and improves the reliability, resilience, availability, fault tolerance, and disaster recovery (DR) of Google Cloud workloads based on the design principles and recommendations in the Reliability pillar of the Google Cloud Well-Architected Framework. Use when the user asks about reliability-related topics like workload uptime, designing for high availability (HA) or DR, setting and meeting RTO/RPO targets, SRE best practices, backup strategies, multi-region failover, or fault-tolerant architecture on Google Cloud. Don't use for other Well-Architected Framework pillars such as Cost Optimization, Operational Excellence, or Security, or for hands-on resource deployment and live incident troubleshooting.

02 资源文件 3

03 SKILL.md 正文

Google Cloud Well-Architected Framework skill for the Reliability 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 Reliability pillar of the Google Cloud Well-Architected Framework provides principles and recommendations to help you design, deploy, and manage reliable, resilient, and highly available workloads in Google Cloud. A reliable system consistently performs its intended functions under defined conditions, is resilient to failures, and recovers gracefully from disruptions, thereby minimizing downtime, enhancing user experience, and ensuring data integrity.

Core principles

The recommendations in the reliability 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 reliability:

  • Compute: Compute Engine Managed Instance Groups (MIGs), Google Kubernetes Engine (GKE), Cloud Run
  • Networking: Cloud Load Balancing, Cloud CDN, Cloud DNS
  • Storage and databases: Cloud Storage (multi-region), Cloud SQL High Availability, Spanner, Filestore, Firestore
  • Operations: Cloud Monitoring, Cloud Logging, Google Cloud Managed Service for Prometheus
  • Disaster recovery: Backup and DR Service, Filestore backups

Workload assessment questions

Ask appropriate questions to understand the reliability-related requirements and constraints of the workload and the user's organization. Choose questions from the following list:

  • How does your organization define and measure the reliability of your systems in relation to user experience?
  • How does your organization approach setting reliability targets for your services?
  • What is your organization's strategy for ensuring high availability through resource redundancy?
  • How does your organization leverage horizontal scalability to maintain performance and reliability?
  • How does your organization utilize observability (metrics, logs, traces) to gain insights and detect potential failures?
  • How does your organization manage alerting based on observability data to ensure timely responses to significant issues without causing alert fatigue?
  • What measures does your organization take to ensure systems can gracefully degrade during high load or partial failures?
  • How frequently and comprehensively does your organization test for recovery from system failures (e.g., regional failovers, release rollbacks)?
  • What is your organization's approach to testing for recovery from data loss?
  • How does your organization conduct and utilize postmortems after incidents?

Validation checklist

Use the following checklist to evaluate the architecture's alignment with reliability recommendations:

  • User-focused SLIs and SLOs are explicitly defined and actively monitored.
  • The architecture avoids single points of failure through cross-zone or cross-region redundancy.
  • Autoscaling is enabled to handle variable demand without manual intervention.
  • Application and infrastructure health checks are configured to trigger automated failovers.
  • Regular backup schedules are in place, and restoration processes are routinely tested.
  • The system architecture incorporates patterns like circuit breakers, retries with exponential backoff, and rate limiting to support graceful degradation.
  • Game days or chaos engineering practices are regularly held to validate failure recovery.
  • A formalized, blameless postmortem process exists to ensure organizational learning from operational incidents.

04 同仓库更多 Skills

tangyixiao
tangyixiao/tangyixiao-skills

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

★ 2
tangyixiao
tangyixiao/tangyixiao-skills

writing-shape

Writing, exploit: shape raw material into an article, paragraph by paragraph.

★ 2
tangyixiao
tangyixiao/tangyixiao-skills

writing-fragments

Writing, explore: mine raw fragments, no structure yet.

★ 2
tangyixiao
tangyixiao/tangyixiao-skills

writing-for-agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

★ 2
tangyixiao
tangyixiao/tangyixiao-skills

writing-clearly-and-concisely

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

★ 2
tangyixiao
tangyixiao/tangyixiao-skills

writing-beats

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

★ 2