Design and deploy global external Application Load Balancers on Google Cloud
Guided 6-step discovery to design and deploy a global external ALB with Cloud CDN caching, Cloud Armor WAF and Service Extensions — workload-mapped configs, Terraform HCL or gcloud scripts
- What
- Guided 6-step discovery to design and deploy a global external ALB with Cloud CDN caching, Cloud Armor WAF and Service Extensions — workload-mapped configs, Terraform HCL or gcloud scripts
- Cost
- Free
- Needs
- a Google Cloud account with billing enabled (deploying the designed configuration provisions REAL cloud infrastructure with REAL costs); gcloud CLI for automated discovery/actuation (design-only mode without it) — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Google's official skill for designing and deploying Google Cloud global external Application Load Balancers: a 6-step discovery process. Step 1, project and protocol/cert basics. Step 2, sequential origin definition — Cloud Storage, Compute Engine MIGs, GKE clusters, Cloud Run services or external IPs/FQDNs — classified by workload type (static assets, cacheable API, uncacheable/transactional, dynamic SSR), then routing rules and CDN logging. Step 3, traffic management and Service Extensions (WASM plugins/callouts). Step 4, workload-mapped Cloud CDN caching (TTL, cache keys, compression, negative caching presets per workload). Step 5, Cloud Armor WAF — rate limiting and OWASP rules calibrated per workload (strict thresholds for login/checkout endpoints). Step 6, review, then emit production-grade Terraform HCL or gcloud CLI scripts, deployed via Infrastructure Manager or bash — with drift detection afterwards. Details stay progressively disclosed; recommended best-practice configs first, advanced knobs only on request. Honest caveats: methodology plus generated IaC — deploying what it designs provisions REAL Google Cloud infrastructure (billing-enabled account required, real cloud costs; deploying anything costs real money); gcloud availability assumed for automated discovery and actuation — without it the skill degrades gracefully to design-only mode. 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
Design and deploy global external Application Load Balancers is a free Muse skill, Google's official skill for designing and deploying Google Cloud global external Application Load Balancers. It follows a six-step discovery process, covering project and protocol basics, origin definition across Cloud Storage, Compute Engine, GKE, Cloud Run or, plus Cloud CDN caching, Cloud Armor WAF and Service Extensions.
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 account with billing enabled (deploying the designed configuration provisions REAL cloud infrastructure with REAL costs); gcloud CLI for automated discovery/actuation (design-only mode without it) — the skill is guidance the agent follows, not software to install Install "Design and deploy global external Application Load Balancers on Google Cloud" for me. It teaches my agent Google's 6-step load-balancer workflow: discover the project, define backends sequentially by workload type (static, cacheable API, transactional, dynamic SSR), propose workload-mapped Cloud CDN caching and Cloud Armor WAF configs, then generate production Terraform HCL or gcloud CLI scripts and deploy via Infrastructure Manager or bash — with drift detection afterwards. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/google/skills/90bb0a8853daa6ab597c303a69d80ad8ee3e44d5/skills/cloud/google-cloud-global-frontend-configuration/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-global-frontend-configuration 1.0.1. What changed since 1.0.0, the version the previous prompt described: SKILL.md gains an Attribution section marked MUST READ, which states the rule inline and points to references/attribution.md for the full instructions. Before executing any gcloud, REST API, or MCP command, the agent must read and follow that file. What it 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-global-frontend-configuration)" set inline on each command, and append agent-skills/1.0 (skill:google-cloud-global-frontend-configuration) 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 6-step discovery workflow, the generated Terraform and gcloud scripts and the drift detection 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-global-frontend-configuration". 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. authenticate gcloud and pick the project; describe the workload to front; remember deploying the generated configuration incurs real Google Cloud costs). 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
- It can run commands on your Muse’s computer.
What the scan found — excerpts from the install prompt
- runs commands — Install "Design and deploy global external Application Load Balancers on Google Cloud" for me. It teaches my a · Installe-moi « Concevoir et déployer des load balancers externes globaux sur Google Cloud ». Il enseigne à mon
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 : runs commands
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.