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

/google-cloud-waf-reliability

@053feb2
Run it yourself

Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework. Use to evaluate a workload, identify reliability requirements, and provide actionable recommendations for building resilient, highly available systems.

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/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

≈75 tokens for metadata: the name and description. ≈1.7k when used: this file.

Description uses 3.8% 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 ≈302 characters, or 3.8%.

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

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.

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.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    The skill provides architectural guidance based on the Google Cloud Well-Architected Framework. It contains no executable code or dangerous instructions and only references official Google documentation.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 053feb2. 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 month
metadata
{
  "source": "google/skills (Apache 2.0)"
}

README badge

README badge for davila7/claude-code-templates/google-cloud-waf-reliability