Google Cloud Waf Reliability
google/skills
Generates guidance for reliability, resilience, availability, redundancy, fault-tolerance, and disaster recovery (DR) for Google Cloud workloads based on the design principles and recommendations in…
Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework.
Install Google Cloud Waf Reliability
$ npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davila7/claude-code-templates google-cloud-waf-reliability --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/development/google-cloud-waf-reliability .claude/skills/google-cloud-waf-reliability && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-cloud-waf-reliability" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliability into .claude/skills/google-cloud-waf-reliability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-cloud-waf-reliability", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliabilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davila7/claude-code-templates google-cloud-waf-reliability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-tool/components/skills/development/google-cloud-waf-reliability .agents/skills/google-cloud-waf-reliability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-cloud-waf-reliability" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliability into .agents/skills/google-cloud-waf-reliability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-cloud-waf-reliability", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davila7/claude-code-templates google-cloud-waf-reliability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-tool/components/skills/development/google-cloud-waf-reliability .cursor/skills/google-cloud-waf-reliability && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-cloud-waf-reliability" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliability into .cursor/skills/google-cloud-waf-reliability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-cloud-waf-reliability", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davila7/claude-code-templates.git --path cli-tool/components/skills/development/google-cloud-waf-reliability--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davila7/claude-code-templates google-cloud-waf-reliability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-tool/components/skills/development/google-cloud-waf-reliability .gemini/skills/google-cloud-waf-reliability && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-cloud-waf-reliability" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliability into .gemini/skills/google-cloud-waf-reliability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-cloud-waf-reliability", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davila7/claude-code-templates google-cloud-waf-reliabilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-tool/components/skills/development/google-cloud-waf-reliability .github/skills/google-cloud-waf-reliability && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-cloud-waf-reliability" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliability into .github/skills/google-cloud-waf-reliability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-cloud-waf-reliability", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davila7/claude-code-templates google-cloud-waf-reliability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-tool/components/skills/development/google-cloud-waf-reliability .opencode/skills/google-cloud-waf-reliability && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-cloud-waf-reliability" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/google-cloud-waf-reliability into .opencode/skills/google-cloud-waf-reliability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-cloud-waf-reliability", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
google-cloud-waf-reliability- GitHub stars
- 32k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 722 words
- Files
- 1
- Skills in repo
- 478
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework.
- Evaluate a workload
- SKILL.md covers Overview, Core principles, Relevant Google Cloud products and Workload assessment questions, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Identify reliability requirements
What it does
Google Cloud Waf Reliability is an agent skill from davila7/claude-code-templates. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Cloud architecture and Site reliability engineering. It works with Google Cloud. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.
When your agent uses it
- Evaluate a workload
- Identify reliability requirements
- Provide actionable recommendations for building resilient
- Highly available systems
Example prompts
- “Use the google-cloud-waf-reliability skill to generate reliability-focused guidance for Google Cloud workloads based on the Google Cloud…”
- “/google-cloud-waf-reliability”
What it can do on your machine
Read from SKILL.md and the folder at commit 46b4d8b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.cloud.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Google Cloud Waf Reliability loads about 1.8k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 722 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from davila7/claude-code-templates at commit 46b4d8b, republished under its MIT licence (© davila7). 722 words, ~1,756 tokens.
Download SKILL.mdSave it as
.claude/skills/google-cloud-waf-reliability/SKILL.md (or your agent's skills folder).- name
- google-cloud-waf-reliability
- description
- 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.
- source
- google/skills (Apache 2.0)
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:
Define reliability based on user-experience goals: Measurement of reliability should reflect the actual experience of the system's users rather than merely relying on infrastructure metrics. Focus on outcomes that matter most to users. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/define-reliability-based-on-user-experience-goals
Set realistic targets for reliability: Determine appropriate Service Level Objectives (SLOs) that balance the cost and complexity of maximizing availability against business requirements. Utilize error budgets to manage feature velocity. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/set-targets
Build highly available systems through resource redundancy: Eliminate single points of failure by duplicating critical components across zones and regions to maintain operations during localized outages. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/build-highly-available-systems
Take advantage of horizontal scalability: Design system architectures to scale horizontally (adding more instances) to seamlessly accommodate load fluctuations and improve overall fault tolerance. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/horizontal-scalability
Detect potential failures by using observability: Implement thorough monitoring, logging, and alerting systems to proactively detect, diagnose, and address anomalies before they cause user-facing issues. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/observability
Design for graceful degradation: Architect systems to maintain critical functionality, even if at reduced performance or with limited features, when dependencies fail or the system experiences extreme stress. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/graceful-degradation
Perform testing for recovery from failures: Build confidence in system resilience by continuously simulating failures and verifying the effectiveness of automated and manual recovery procedures. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures
Perform testing for recovery from data loss: Regularly test backup and restore protocols to ensure rapid recovery from data corruption or loss, remaining within the defined Recovery Time Objective (RTO) and Recovery Point Objective (RPO). Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-data-loss
Conduct thorough postmortems: Foster a blameless culture by investigating outages comprehensively to understand root causes, followed by implementing measures that prevent recurrence. Grounding document: https://docs.cloud.google.com/architecture/framework/reliability/conduct-postmortems
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
Show full SKILL.md (287 more words)Show less
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.
© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in cli-tool/components/skills/development/google-cloud-waf-reliability of davila7/claude-code-templates.
Open the folder on GitHubat commit 46b4d8b
Compare with similar skills
Google Cloud Waf Reliability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Cloud Waf Reliability this skilldavila7/claude-code-templates | 32k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Google Cloud Waf Reliabilitygoogle/skills | 21k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Cloud Cost Optimizationwshobson/agents | 40k | 14 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Thesvgglincker/thesvg | 2.8k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Dangling DNS Finderanirudhbiyani/findmytakeover | 180 | — | ~1.8k | Automated safety check: Pass | GPL-3.0 | |
| Terraform Module Librarywshobson/agents | 40k | 11 repos | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Cloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
Thesvg
glincker/thesvg
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.
Dangling DNS Finder
anirudhbiyani/findmytakeover
Detect dangling DNS records and subdomain-takeover risks across a multi-cloud environment by running the bundled findmytakeover tool.
Terraform Module Library
wshobson/agents
Build reusable, tested Terraform modules for AWS, Azure, GCP and OCI, with a standard file layout, an AWS VPC example, versioning rules and Terratest checks.
GCP DrawIO Diagram Generator
a5c-ai/babysitter
Creates DrawIO XML diagrams of Google Cloud architectures from text or images, and analyzes existing .drawio files to list their GCP components.
More from davila7/claude-code-templates
All 478 skills in this repoPerplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Neuropixels Data Analysis
davila7/claude-code-templates
Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
CAPA Officer
davila7/claude-code-templates
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Related
Works with
Categories
Questions about Google Cloud Waf Reliability
What does Google Cloud Waf Reliability do?
Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework. Google Cloud Waf Reliability is an agent skill from davila7/claude-code-templates. Generates reliability-focused guidance for Google Cloud workloads based on the Google Cloud Well-Architected Framework.
When should I use Google Cloud Waf Reliability?
Google Cloud Waf Reliability fits situations like: evaluate a workload; identify reliability requirements; provide actionable recommendations for building resilient; highly available systems.
How do I install Google Cloud Waf Reliability in Claude Code?
Run `npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a claude-code`. Or copy the skill folder (cli-tool/components/skills/development/google-cloud-waf-reliability in davila7/claude-code-templates) into .claude/skills/google-cloud-waf-reliability in your project. Claude Code loads it when a task matches its description.
How do I install Google Cloud Waf Reliability in Codex?
Run `npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a codex`. Or copy the skill folder (cli-tool/components/skills/development/google-cloud-waf-reliability in davila7/claude-code-templates) into .agents/skills/google-cloud-waf-reliability in your project. Codex loads it when a task matches its description.
Can I use Google Cloud Waf Reliability in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill google-cloud-waf-reliability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-cloud-waf-reliability, .gemini/skills/google-cloud-waf-reliability, .github/skills/google-cloud-waf-reliability and .opencode/skills/google-cloud-waf-reliability in your project.
What does Google Cloud Waf Reliability need to run?
SKILL.md names no scripts, command-line tools or credentials: Google Cloud Waf Reliability is instructions for the agent only.
Does Google Cloud Waf Reliability access the network?
SKILL.md names 1 domain. As links in the text: docs.cloud.google.com. This is read from the text; nothing was executed.
Is Google Cloud Waf Reliability safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Google Cloud Waf Reliability use?
Google Cloud Waf Reliability is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Google Cloud Waf Reliability use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Google Cloud Waf Reliability?
Skills that share tags, products or a category with Google Cloud Waf Reliability: Google Cloud Waf Reliability (google/skills, 21k stars), Cloud Cost Optimization (wshobson/agents, 40k stars), Thesvg (glincker/thesvg, 2.8k stars) and Dangling DNS Finder (anirudhbiyani/findmytakeover, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Cloud Waf Reliability?
davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,483 GitHub stars. The repository holds 478 skills in this directory. The repository was last updated on October 9, 2026.
Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.