[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6995HSADCV7FH47KTAK2YJN":3,"skill-same:01M6995HSADCV7FH47KTAK2YJN":109},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6995HSADCV7FH47KTAK2YJN","google-cloud-global-frontend-configuration",null,"Guides agents through a 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers with Cloud CDN, Cloud Armor, and Service Extensions, mapping workload requirements to best-practice configurations.\nUse when:\n- Designing, configuring, or deploying a Google Cloud global external Application Load Balancer, Cloud CDN, Cloud Armor WAF, or Service Extensions.\n- Discovering existing Google Cloud resources (Cloud Storage, MIGs, GKE, Cloud Run) to use as backends.\n- Generating production-grade Terraform HCL or gcloud CLI scripts for global external Application Load Balancers.\n- Actuating deployments via Infrastructure Manager or bash scripts, including IAM pre-checks.\n- Detecting, analyzing, or reconciling configuration drift on deployed global external Application Load Balancers.\nDon't use for:\n- Non-Google Cloud load balancing or security configurations.\n- Purely regional or internal load balancing setups (unless part of a hybrid\u002Ffailover global design).","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[9,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"google cloud global frontend configuration","google cloud","frontend","cloud","configuration","global","run","gke","iam","guides","drift","Bash","when","load balancer","Cloud Storage","detecting","resources","gcloud","security","cli","design","2026-11-10 10:12:30",false,"---\nname: google-cloud-global-frontend-configuration\nmetadata:\n  version: \"1.0.2\"\n  category: Networking\ndescription: |\n  Guides agents through a 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers with Cloud CDN, Cloud Armor, and Service Extensions, mapping workload requirements to best-practice configurations.\n  Use when:\n  - Designing, configuring, or deploying a Google Cloud global external Application Load Balancer, Cloud CDN, Cloud Armor WAF, or Service Extensions.\n  - Discovering existing Google Cloud resources (Cloud Storage, MIGs, GKE, Cloud Run) to use as backends.\n  - Generating production-grade Terraform HCL or gcloud CLI scripts for global external Application Load Balancers.\n  - Actuating deployments via Infrastructure Manager or bash scripts, including IAM pre-checks.\n  - Detecting, analyzing, or reconciling configuration drift on deployed global external Application Load Balancers.\n  Don't use for:\n  - Non-Google Cloud load balancing or security configurations.\n  - Purely regional or internal load balancing setups (unless part of a hybrid\u002Ffailover global design).\n---\n\n# Google Cloud global external Application Load Balancer Configuration Skill\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:google-cloud-global-frontend-configuration)\"`\nand append\n`agent-skills\u002F1.0 (skill:google-cloud-global-frontend-configuration)`\nto `User-Agent` headers.\n\n## Purpose & Agent Guidance\n\nThis skill enables the agent to guide users through a structured, 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers (incorporating Cloud CDN, Cloud Armor, and Service Extensions).\n\n**Assumptions & Target Environments:**\n- This skill assumes it is called from environments (such as Gemini CLI, Antigravity, etc.) where the Google Cloud CLI (`gcloud`) can be executed.\n- If `gcloud` is not available or accessible, the skill cannot perform automated resource discovery or managed deployment actuation. In such environments, the skill will limit its support to guiding the design and generating Terraform HCL configurations.\n\nWhen executing this skill, the agent must:\n- Map user workload requirements to simplified, opinionated best-practice configurations using actual Google Cloud product names.\n- Progressively disclose details, hiding advanced complexity unless the user explicitly asks for customization.\n- Leverage the reference documents in the `references\u002F` directory to perform resource discovery, code generation, actuation, and drift detection.\n\n## The 6-Step Configuration Flow\n\n### Step 1: Basics\n*   **Project Discovery:** Consult `references\u002Fresource-discovery.md` to auto-detect the Google Cloud project ID. Present the discovered project ID to the user.\n*   Ask the user for the foundational details of their load balancer:\n    *   **Name & Description:** What should we call this load balancer?\n    *   **Protocol Selection:** Do they need HTTP, HTTPS, or both?\n    *   **Certificate Management:** Do they want to use Google-managed certificates or bring their own existing certificates?\n\n### Step 2: Origin Configuration\nHelp the user define their backend workloads through a strictly sequential, step-by-step loop. Do NOT ask everything at once. All steps are mandatory.\n\n*   **Sub-step A - Origin Setup:** Ask if they have a single origin or need multi-origin support. Wait for response.\n*   **Sub-step B - Origin Types:** Ask them to select the backend types from: Cloud Storage Buckets, Compute Engine Managed Instance Groups (MIGs), Google Kubernetes Engine (GKE) Clusters, Cloud Run Services, or External\u002FInternet origins (IP\u002FFQDN). Wait for response.\n*   **Sub-step C - Origin Definition Loop:** Execute the following loop sequentially for EACH origin type selected in Sub-step B. Wait for the user to answer for one origin before asking about the next:\n    *   **Resource Discovery:** For Google Cloud-native origins (Cloud Storage, MIGs, GKE, Cloud Run), consult `references\u002Fresource-discovery.md` to fetch resources. Present the list starting with **1. Create New**, **2. NA**. For External\u002FInternet origins, just ask for the FQDN\u002FIP.\n    *   **Workload Type (CRITICAL):** Immediately after they define the resource, ask exactly what type of workload is being served:\n        1.  **Static Images \u002F Objects** (Static content, images, videos, styling assets)\n        2.  **Cacheable API** (Read-only, public APIs where cached data is acceptable)\n        3.  **Uncacheable API \u002F Transactions** (Transactional endpoints, login, checkout, account changes)\n        4.  **Dynamic Web (SSR)** (Dynamic pages, server-side rendered apps, custom dynamic sessions)\n*   **Sub-step D - Routing Rules:** Once ALL origins have been fully defined one by one, ask how traffic should be routed between them (Path-based, header-based, or query-param-based). Wait for response.\n*   **Sub-step E - Logging:** After routing is established, ask if they want to enable Cloud CDN logging, and if so, at what sampling rate (0-100%). Wait for response.\n\n### Step 3: Traffic Management & Extensibility\n*   Provide a brief summary of the origins and routing rules defined in Step 2.\n*   Ask if they need to enable Advanced Traffic Management settings (such as granular weighted load balancing, traffic mirroring, or **Cloud Load Balancing Service Extensions** for custom WASM plugins \u002F callouts), or if they want to proceed with **Google Cloud Best Practice Configuration**.\n\n### Step 4: Caching (Cloud CDN)\nPropose a \"Recommended Configuration\" based entirely on the Workload Type from Step 2. Do not list the advanced settings (TTL, Cache Keys, Compression) unless they reject the recommendation and want to customize.\n\n*   **If Workload = Static Images \u002F Objects:**\n    *   Cache Mode: Cache All Static\n    *   TTL: Client (1 day \u002F 86400s), Default (30 days \u002F 2592000s), Max (365 days \u002F 31536000s) — balances long-term cache offload for static assets with periodic re-validation.\n    *   Cache Key: Backend services use Protocol + Host + Path (Ignore Query\n        Strings); Cloud Storage backend buckets omit Protocol and Host (Object\n        Path + Cloud Storage query parameters only)\n    *   Compression: Enabled (Brotli & Gzip)\n    *   Negative Caching: Enabled\n    *   Serve while stale: Enabled\n*   **If Workload = Cacheable API:**\n    *   Cache Mode: Use Origin Headers\n    *   TTL: Managed by Origin (Omitted from configuration to prevent errors)\n    *   Cache Key: Protocol + Host + Path + Include Query Strings\n    *   Compression: Enabled (Gzip)\n    *   Negative Caching: Enabled\n    *   Serve while stale: Disabled\n*   **If Workload = Uncacheable API \u002F Transactions:**\n    *   Cache Mode: Disabled (CDN Bypassed)\n*   **If Workload = Dynamic Web (SSR):**\n    *   Cache Mode: Use Origin Headers\n    *   TTL: Managed by Origin (Omitted from configuration to prevent errors)\n    *   Cache Key: Protocol + Host + Path\n    *   Compression: Enabled (Brotli & Gzip)\n    *   Cache Bypass: Bypass cache if session cookies (e.g., SESSID, JWT) are present\n\n### Step 5: Security (Cloud Armor)\nPropose a \"Recommended Configuration\" based entirely on the Workload Type from Step 2. Keep advanced protection (Bot Management, Threat Intel, Geo-blocking) hidden unless requested.\n\n*   **If Workload = Static Images \u002F Objects:**\n    *   Rate Limiting: None (Standard Edge behavior; rate limiting is unsupported on Cloud Armor Edge policies for Cloud Storage buckets).\n    *   OWASP Protection: Disabled\n*   **If Workload = Cacheable API:**\n    *   Rate Limiting: 100 requests per minute per client IP (standard baseline to prevent API abuse and DDoS while accommodating normal interactive usage).\n    *   OWASP Protection: Enabled (SQLi, XSS, Local File Inclusion)\n*   **If Workload = Uncacheable API \u002F Transactions:**\n    *   Rate Limiting: Strict 30 requests per minute per client IP (tight threshold to protect sensitive transactional endpoints like login\u002Fcheckout from credential stuffing and brute-force attacks).\n    *   OWASP Protection: Enabled (SQLi, XSS, Remote Command Execution, Session Fixation)\n    *   Bot Management & Threat Intel: Enabled (Block malicious bots and known malicious IPs)\n*   **If Workload = Dynamic Web (SSR):**\n    *   Rate Limiting: 120 requests per minute per client IP (generous threshold to accommodate burst requests for initial page loads and asset hydration in SSR web applications).\n    *   OWASP Protection: Enabled (SQLi, XSS, CSRF, Shellshock)\n    *   Geo-blocking: Optional (Restrict\u002Fallow specific country access)\n\n### Step 6: Review & Deploy\n*   **Configuration Summary:** Generate a complete, formatted markdown table showing all finalized settings from Steps 1 through 5, using Google Cloud product names. Follow this exact template structure:\n\n    | Component | Parameter \u002F Setting | Value & Justification |\n    | :--- | :--- | :--- |\n    | **Load Balancer** | Name & Protocol | `\u003CName>` (HTTP\u002FHTTPS) |\n    | **Origins** | Backends & Workloads | `\u003CBackend 1>` (`\u003CWorkload Type>`), `\u003CBackend 2>`... |\n    | **Traffic Management** | Routing Rules | `\u003CPath \u002F Header rules or Default>` |\n    | **Cloud CDN** | Cache Mode & TTLs | `\u003CCache Mode>`, Default TTL: `\u003CTTL>` |\n    | **Cloud Armor** | Rate Limiting & OWASP | `\u003CRPM Limit>`, OWASP Rules: `\u003CEnabled\u002FDisabled>` |\n    | **Service Extensions**| WASM \u002F Callouts | `\u003CEnabled\u002FDisabled or N\u002FA>` |\n\n*   **Next Action:** Ask the user to choose their deployment\u002Fgeneration format (Terraform HCL or gcloud CLI Bash Script) and their next action:\n    1.  **Show Code \u002F Script** (Display the HCL code or gcloud bash script. Once displayed, offer options to **Download** or **Deploy\u002FExecute**)\n    2.  **Download files** (Save `main.tf` or `deploy.sh` to the local workspace)\n    3.  **Deploy Configuration:** Initiate the deployment via Infrastructure Manager or execute the gcloud script. This should be done using the deployment instructions in `references\u002Fmanaged-deployment.md`.\n\n---\n\n## Relevant Documentation & Supportive Links\n- [Cloud Load Balancing Overview](https:\u002F\u002Fcloud.google.com\u002Fload-balancing\u002Fdocs\u002Fload-balancing-overview)\n- [Cloud CDN Documentation](https:\u002F\u002Fcloud.google.com\u002Fcdn\u002Fdocs)\n- [Cloud Armor Documentation](https:\u002F\u002Fcloud.google.com\u002Farmor\u002Fdocs)\n- [Cloud Load Balancing Service Extensions](https:\u002F\u002Fcloud.google.com\u002Fservice-extensions\u002Fdocs\u002Foverview)\n- [Infrastructure Manager Overview](https:\u002F\u002Fcloud.google.com\u002Finfrastructure-manager\u002Fdocs)\n- [Official Terraform LB-HTTP Module](https:\u002F\u002Fregistry.terraform.io\u002Fmodules\u002FGoogleCloudPlatform\u002Flb-http\u002Fgoogle\u002Flatest)\n- [Official Terraform Cloud Armor Module](https:\u002F\u002Fregistry.terraform.io\u002Fmodules\u002FGoogleCloudPlatform\u002Fcloud-armor\u002Fgoogle\u002Flatest)\n","# Google Cloud global external Application Load Balancer Configuration Skill\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:google-cloud-global-frontend-configuration)\"`\nand append\n`agent-skills\u002F1.0 (skill:google-cloud-global-frontend-configuration)`\nto `User-Agent` headers.\n\n## Purpose & Agent Guidance\n\nThis skill enables the agent to guide users through a structured, 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers (incorporating Cloud CDN, Cloud Armor, and Service Extensions).\n\n**Assumptions & Target Environments:**\n- This skill assumes it is called from environments (such as Gemini CLI, Antigravity, etc.) where the Google Cloud CLI (`gcloud`) can be executed.\n- If `gcloud` is not available or accessible, the skill cannot perform automated resource discovery or managed deployment actuation. In such environments, the skill will limit its support to guiding the design and generating Terraform HCL configurations.\n\nWhen executing this skill, the agent must:\n- Map user workload requirements to simplified, opinionated best-practice configurations using actual Google Cloud product names.\n- Progressively disclose details, hiding advanced complexity unless the user explicitly asks for customization.\n- Leverage the reference documents in the `references\u002F` directory to perform resource discovery, code generation, actuation, and drift detection.\n\n## The 6-Step Configuration Flow\n\n### Step 1: Basics\n*   **Project Discovery:** Consult `references\u002Fresource-discovery.md` to auto-detect the Google Cloud project ID. Present the discovered project ID to the user.\n*   Ask the user for the foundational details of their load balancer:\n    *   **Name & Description:** What should we call this load balancer?\n    *   **Protocol Selection:** Do they need HTTP, HTTPS, or both?\n    *   **Certificate Management:** Do they want to use Google-managed certificates or bring their own existing certificates?\n\n### Step 2: Origin Configuration\nHelp the user define their backend workloads through a strictly sequential, step-by-step loop. Do NOT ask everything at once. All steps are mandatory.\n\n*   **Sub-step A - Origin Setup:** Ask if they have a single origin or need multi-origin support. Wait for response.\n*   **Sub-step B - Origin Types:** Ask them to select the backend types from: Cloud Storage Buckets, Compute Engine Managed Instance Groups (MIGs), Google Kubernetes Engine (GKE) Clusters, Cloud Run Services, or External\u002FInternet origins (IP\u002FFQDN). Wait for response.\n*   **Sub-step C - Origin Definition Loop:** Execute the following loop sequentially for EACH origin type selected in Sub-step B. Wait for the user to answer for one origin before asking about the next:\n    *   **Resource Discovery:** For Google Cloud-native origins (Cloud Storage, MIGs, GKE, Cloud Run), consult `references\u002Fresource-discovery.md` to fetch resources. Present the list starting with **1. Create New**, **2. NA**. For External\u002FInternet origins, just ask for the FQDN\u002FIP.\n    *   **Workload Type (CRITICAL):** Immediately after they define the resource, ask exactly what type of workload is being served:\n        1.  **Static Images \u002F Objects** (Static content, images, videos, styling assets)\n        2.  **Cacheable API** (Read-only, public APIs where cached data is acceptable)\n        3.  **Uncacheable API \u002F Transactions** (Transactional endpoints, login, checkout, account changes)\n        4.  **Dynamic Web (SSR)** (Dynamic pages, server-side rendered apps, custom dynamic sessions)\n*   **Sub-step D - Routing Rules:** Once ALL origins have been fully defined one by one, ask how traffic should be routed between them (Path-based, header-based, or query-param-based). Wait for response.\n*   **Sub-step E - Logging:** After routing is established, ask if they want to enable Cloud CDN logging, and if so, at what sampling rate (0-100%). Wait for response.\n\n### Step 3: Traffic Management & Extensibility\n*   Provide a brief summary of the origins and routing rules defined in Step 2.\n*   Ask if they need to enable Advanced Traffic Management settings (such as granular weighted load balancing, traffic mirroring, or **Cloud Load Balancing Service Extensions** for custom WASM plugins \u002F callouts), or if they want to proceed with **Google Cloud Best Practice Configuration**.\n\n### Step 4: Caching (Cloud CDN)\nPropose a \"Recommended Configuration\" based entirely on the Workload Type from Step 2. Do not list the advanced settings (TTL, Cache Keys, Compression) unless they reject the recommendation and want to customize.\n\n*   **If Workload = Static Images \u002F Objects:**\n    *   Cache Mode: Cache All Static\n    *   TTL: Client (1 day \u002F 86400s), Default (30 days \u002F 2592000s), Max (365 days \u002F 31536000s) — balances long-term cache offload for static assets with periodic re-validation.\n    *   Cache Key: Backend services use Protocol + Host + Path (Ignore Query\n        Strings); Cloud Storage backend buckets omit Protocol and Host (Object\n        Path + Cloud Storage query parameters only)\n    *   Compression: Enabled (Brotli & Gzip)\n    *   Negative Caching: Enabled\n    *   Serve while stale: Enabled\n*   **If Workload = Cacheable API:**\n    *   Cache Mode: Use Origin Headers\n    *   TTL: Managed by Origin (Omitted from configuration to prevent errors)\n    *   Cache Key: Protocol + Host + Path + Include Query Strings\n    *   Compression: Enabled (Gzip)\n    *   Negative Caching: Enabled\n    *   Serve while stale: Disabled\n*   **If Workload = Uncacheable API \u002F Transactions:**\n    *   Cache Mode: Disabled (CDN Bypassed)\n*   **If Workload = Dynamic Web (SSR):**\n    *   Cache Mode: Use Origin Headers\n    *   TTL: Managed by Origin (Omitted from configuration to prevent errors)\n    *   Cache Key: Protocol + Host + Path\n    *   Compression: Enabled (Brotli & Gzip)\n    *   Cache Bypass: Bypass cache if session cookies (e.g., SESSID, JWT) are present\n\n### Step 5: Security (Cloud Armor)\nPropose a \"Recommended Configuration\" based entirely on the Workload Type from Step 2. Keep advanced protection (Bot Management, Threat Intel, Geo-blocking) hidden unless requested.\n\n*   **If Workload = Static Images \u002F Objects:**\n    *   Rate Limiting: None (Standard Edge behavior; rate limiting is unsupported on Cloud Armor Edge policies for Cloud Storage buckets).\n    *   OWASP Protection: Disabled\n*   **If Workload = Cacheable API:**\n    *   Rate Limiting: 100 requests per minute per client IP (standard baseline to prevent API abuse and DDoS while accommodating normal interactive usage).\n    *   OWASP Protection: Enabled (SQLi, XSS, Local File Inclusion)\n*   **If Workload = Uncacheable API \u002F Transactions:**\n    *   Rate Limiting: Strict 30 requests per minute per client IP (tight threshold to protect sensitive transactional endpoints like login\u002Fcheckout from credential stuffing and brute-force attacks).\n    *   OWASP Protection: Enabled (SQLi, XSS, Remote Command Execution, Session Fixation)\n    *   Bot Management & Threat Intel: Enabled (Block malicious bots and known malicious IPs)\n*   **If Workload = Dynamic Web (SSR):**\n    *   Rate Limiting: 120 requests per minute per client IP (generous threshold to accommodate burst requests for initial page loads and asset hydration in SSR web applications).\n    *   OWASP Protection: Enabled (SQLi, XSS, CSRF, Shellshock)\n    *   Geo-blocking: Optional (Restrict\u002Fallow specific country access)\n\n### Step 6: Review & Deploy\n*   **Configuration Summary:** Generate a complete, formatted markdown table showing all finalized settings from Steps 1 through 5, using Google Cloud product names. Follow this exact template structure:\n\n    | Component | Parameter \u002F Setting | Value & Justification |\n    | :--- | :--- | :--- |\n    | **Load Balancer** | Name & Protocol | `\u003CName>` (HTTP\u002FHTTPS) |\n    | **Origins** | Backends & Workloads | `\u003CBackend 1>` (`\u003CWorkload Type>`), `\u003CBackend 2>`... |\n    | **Traffic Management** | Routing Rules | `\u003CPath \u002F Header rules or Default>` |\n    | **Cloud CDN** | Cache Mode & TTLs | `\u003CCache Mode>`, Default TTL: `\u003CTTL>` |\n    | **Cloud Armor** | Rate Limiting & OWASP | `\u003CRPM Limit>`, OWASP Rules: `\u003CEnabled\u002FDisabled>` |\n    | **Service Extensions**| WASM \u002F Callouts | `\u003CEnabled\u002FDisabled or N\u002FA>` |\n\n*   **Next Action:** Ask the user to choose their deployment\u002Fgeneration format (Terraform HCL or gcloud CLI Bash Script) and their next action:\n    1.  **Show Code \u002F Script** (Display the HCL code or gcloud bash script. Once displayed, offer options to **Download** or **Deploy\u002FExecute**)\n    2.  **Download files** (Save `main.tf` or `deploy.sh` to the local workspace)\n    3.  **Deploy Configuration:** Initiate the deployment via Infrastructure Manager or execute the gcloud script. This should be done using the deployment instructions in `references\u002Fmanaged-deployment.md`.\n\n---\n\n## Relevant Documentation & Supportive Links\n- [Cloud Load Balancing Overview](https:\u002F\u002Fcloud.google.com\u002Fload-balancing\u002Fdocs\u002Fload-balancing-overview)\n- [Cloud CDN Documentation](https:\u002F\u002Fcloud.google.com\u002Fcdn\u002Fdocs)\n- [Cloud Armor Documentation](https:\u002F\u002Fcloud.google.com\u002Farmor\u002Fdocs)\n- [Cloud Load Balancing Service Extensions](https:\u002F\u002Fcloud.google.com\u002Fservice-extensions\u002Fdocs\u002Foverview)\n- [Infrastructure Manager Overview](https:\u002F\u002Fcloud.google.com\u002Finfrastructure-manager\u002Fdocs)\n- [Official Terraform LB-HTTP Module](https:\u002F\u002Fregistry.terraform.io\u002Fmodules\u002FGoogleCloudPlatform\u002Flb-http\u002Fgoogle\u002Flatest)\n- [Official Terraform Cloud Armor Module](https:\u002F\u002Fregistry.terraform.io\u002Fmodules\u002FGoogleCloudPlatform\u002Fcloud-armor\u002Fgoogle\u002Flatest)\n",{"name":5,"metadata":53,"description":7},{"version":54,"category":55},"1.0.2","Networking","main","4c6800d20130b5a3233e414609f1241013cec8cc","skills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration",2005,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 01:51:35",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add google\u002Fskills --skill google-cloud-global-frontend-configuration",{"tool":71,"command":72},"bunx","bunx skills add google\u002Fskills --skill google-cloud-global-frontend-configuration",{"tool":74,"command":75},"pnpm","pnpm dlx skills add google\u002Fskills --skill google-cloud-global-frontend-configuration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002FSKILL.md",true,[79,85,89,93,97,101,105],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fattribution.md","REFERENCE","参考文档",1974,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fattribution.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fdrift-detection.md",3024,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fdrift-detection.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fgcloud-generation.md",7089,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fgcloud-generation.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fmanaged-deployment.md",3948,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fmanaged-deployment.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fresource-discovery.md",1746,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fresource-discovery.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fterraform-generation.md",6721,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fterraform-generation.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fterraform-module.md",6279,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgoogle-cloud-global-frontend-configuration\u002Freferences\u002Fterraform-module.md",[110,141,172,201,228,253],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":120,"publishedAt":48},"01M6998S2EZKD3GEJ7F943RZTE","sign-in-with-google-web","Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS \u002F `https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fclient`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React\u002FNext.js\u002FAngular\u002FHTML, verifying ID tokens on backend runtimes (Python\u002FNode.js\u002FGo\u002FJava), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fintermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android\u002FiOS native Credential Manager.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fsign-in-with-google-web\u002FSKILL.md",[116,117],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[9,121,122,123,124,125,126,45,127,28,128,129,130,131,132,35,133,134,135,136,137,138,139,140],"sign in with google web","sign","with","web","android","go","google workspace","implement","policy","python","implementing","react","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":156,"publishedAt":48},"01M6998PHPDCAD684VW5WRG83D","dpop-adoption","Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com\u002Ftoken. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM \u002F service account authentication.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fdpop-adoption\u002FSKILL.md",[147,148,151],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[157,158,9,28,159,160,161,162,163,164,35,165,166,167,168,169,170,137,140,171,39],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":184,"publishedAt":48},"01M6998M72TC73EEAQH4XC7EXW","retrieving-developer-knowledge","Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI\u002FGemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fretrieving-developer-knowledge\u002FSKILL.md",[178,179,182,183],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},[185,186,187,188,28,189,190,191,192,193,194,195,196,39,197,198,199,35,200,133],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":48},"01M6998J2CZEXS9BES9S3WWFKC","migrate-to-rust","Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure\u002Ffix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fmigrate-to-rust\u002FSKILL.md",[],[208,209,210,211,212,213,214,215,130,216,217,218,219,220,221,194,222,223,224,39,225,226,199,227],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":237,"publishedAt":48},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills","Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[234,235,236],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},[9,238,239,240,241,171,242,243,244,245,246,161,247,248,249,195,250,251,39,252,198],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","use","database","candidate",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":257,"categories":258,"keywords":261,"publishedAt":48},"01M6998DWNHTH0BS6W1CY8ZXMP","workload-manager-basics","Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fworkload-manager-basics\u002FSKILL.md",[259,260],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},[262,263,136,264,9,188,46,28,189,265,266,43,267,39,268,198,35,269,270,271,33],"workload manager basics","workload","basics","review","vpc","inspect","you","create","libraries","server"]