Google Cloud WAF — performance optimization
Evaluate Google Cloud workloads against the Well-Architected Framework performance pillar — resource planning, elasticity, modular design, monitoring
- What
- Evaluate Google Cloud workloads against the Well-Architected Framework performance pillar — resource planning, elasticity, modular design, monitoring
- Cost
- Free
- Needs
- a Google Cloud workload to evaluate (or one being designed); nothing else — the skill is guidance and assessment, it provisions or changes nothing itself
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @google's official skill for the Performance Optimization pillar of the Google Cloud Well-Architected Framework: it makes the agent apply the four core principles to a workload — plan resource allocation (matching compute/storage/network to workload requirements), take advantage of elasticity (autoscaling, serverless, scale-to-zero), promote modular design (loosely coupled components that scale and optimize independently), and continuously monitor and improve (observability, tracing, profiling, KPIs feeding iterative enhancement). Includes workload assessment questions per principle, relevant Google Cloud products and features (Compute Engine MIGs, GKE, Cloud Run, Cloud CDN, Memorystore, Bigtable, Spanner, Cloud Trace, Cloud Profiler, Cloud Monitoring), and a validation checklist covering provisioning based on load testing, multi-layer caching, circuit breakers, auto-scaling rules, and idle-overhead reviews. Honest caveats: guidance and assessment only — it does not provision or change cloud resources itself; product recommendations follow Google Cloud docs and may drift; Apache-2.0 licensed. Updated October 22, 2026 (version 1.0.1): SKILL.md now carries an Attribution section marked MUST READ — before any gcloud, REST API or MCP command, the agent must read references/attribution.md; the tag itself identifies only the skill and its version, carries no user data, applies to direct terminal commands only, is never persisted, and an opt-out is documented. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version: 1.0.1
Quick answer
Google Cloud WAF Performance Optimization is a free Muse skill that tunes Google Cloud Armor WAF rules for speed without dropping protection. It optimizes WAF rule evaluation order, rule complexity, and caching strategy, so your security rules run faster and your traffic keeps its protection, instead of trading safety for latency or latency for safety.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 90bb0a8Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Google Cloud workload to evaluate (or one being designed); nothing else — the skill is guidance and assessment, it provisions or changes nothing itself Install "Google Cloud WAF — performance optimization" for me. It gives the agent @google's official playbook for the Well-Architected Framework performance pillar: the four core principles (plan resource allocation, take advantage of elasticity, promote modular design, continuously monitor and improve), workload assessment questions, the relevant Google Cloud products (MIGs, GKE, Cloud Run, Cloud CDN, Memorystore, Bigtable, Spanner, Cloud Trace, Cloud Profiler, Cloud Monitoring), and a validation checklist. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/google/skills/90bb0a8853daa6ab597c303a69d80ad8ee3e44d5/skills/cloud/google-cloud-waf-performance-optimization/SKILL.md Pinned version: install the code at commit 90bb0a8853daa6ab597c303a69d80ad8ee3e44d5 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 22, 2026: Skill Harbor regenerated this install prompt for google-cloud-waf-performance-optimization 1.0.1. What changed since 1.0.0, the version the previous prompt described: SKILL.md gains an Attribution section marked MUST READ — before executing any gcloud, REST API, or MCP command, the agent must read and follow references/attribution.md. What that file requires, stated here so nothing is a surprise: for commands executed directly in the terminal — never in generated scripts, Terraform, or user code — prefix gcloud with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:google-cloud-waf-performance-optimization)" set inline on each command, and append agent-skills/1.0 (skill:google-cloud-waf-performance-optimization) to the User-Agent of direct HTTP, REST or MCP requests. The tag identifies only the skill and its version and carries no user data; it must never be persisted with gcloud config set (that would mislabel unrelated later usage); and references/attribution.md documents a user opt-out — if I ask to disable attribution tagging, omit the variable and the User-Agent suffix. Nothing else in what the skill does changed: the four principles, the workload assessment questions, the product guidance and the validation checklist are the same. 1. Fetch the SKILL.md file and the helper files (including the references/ folder) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "google-cloud-waf-performance-optimization". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the workload or architecture to assess). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 90bb0a8 · 2026-10-22
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-22 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.