Index of every page on this site: llms.txt
All skills
google avatar

/google-cloud-waf-reliability

@5fb62c2
by googlegoogle/skills24k stars
2,026
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/google/skills/google-cloud-waf-reliability

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈190 tokens for metadata: the name and description. ≈2.3k when used: this file. ≈483 more on demand in 1 file.

Description uses 9.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈760 characters, or 9.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Google Cloud Well-Architected Framework skill for the Reliability pillar

Usage 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. For focused inquiries, choose the most relevant questions from the following list; when preparing a comprehensive reliability assessment across a workload, cover all core principles and include the full set of discovery questions under each principle so key operational practices aren't overlooked:

  • Define reliability based on user-experience goals:

    • How does your organization define and measure the reliability of your systems in relation to user experience?
    • How do you define reliability for your application in a way that is meaningful to your end-users?
    • What tools and processes do you use to gather direct user feedback on reliability and performance?
  • Set realistic targets for reliability:

    • How does your organization approach setting reliability targets for your services?
    • What's your process for reviewing and adjusting your SLOs?
  • Build highly available systems through resource redundancy:

    • What is your organization's strategy for ensuring high availability through resource redundancy?
    • What's your strategy for distributing workloads across different geographic regions or availability zones?
  • Take advantage of horizontal scalability:

    • How does your organization leverage horizontal scalability to maintain performance and reliability?
    • How do you monitor for performance bottlenecks that might prevent your system from scaling effectively?
  • Detect potential failures by using observability:

    • 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?
  • Design for graceful degradation:

    • What measures does your organization take to ensure systems can gracefully degrade during high load or partial failures?
    • How are the impacts of degraded performance on user experience measured and mitigated?
    • How is user experience prioritized during periods of degradation?
  • Perform testing for recovery from failures:

    • How frequently and comprehensively does your organization test for recovery from system failures (e.g., regional failovers, release rollbacks)?
  • Perform testing for recovery from data loss:

    • What is your organization's approach to testing for recovery from data loss?
  • Conduct thorough postmortems:

    • How does your organization conduct and utilize postmortems after incidents?
    • Can you share a key learning or a system change that resulted from a recent postmortem?

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert6d3 checks · Risk SAFE
  • Gen Agent Trust Hub6d

    This skill provides architectural guidance based on the Google Cloud Well-Architected Framework's Reliability pillar. It includes links to official Google documentation and a standard usage attribution mechanism for cloud commands. No security issues were detected during the analysis.

  • Socket6d

    No alerts

  • Snyk6d

    Risk: CRITICAL · 1 issue

Signed by skilld at 5fb62c2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week
metadata
{
  "version": "1.1.0",
  "category": "WellArchitectedFramework"
}

README badge

README badge for google/skills/google-cloud-waf-reliability