skilld
All skills
google avatar

/google-cloud-global-frontend-configuration

@becc4b8
by googlegoogle/skills21k stars
1,698

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. Use when: - Designing, configuring, or deploying a Google Cloud global external Application Load Balancer, Cloud CDN, Cloud Armor WAF, or Service Extensions. - Discovering existing Google Cloud resources (Cloud Storage, MIGs, GKE, Cloud Run) to use as backends. - Generating production-grade Terraform HCL or gcloud CLI scripts for global external Application Load Balancers. - Actuating deployments via Infrastructure Manager or bash scripts, including IAM pre-checks. - Detecting, analyzing, or reconciling configuration drift on deployed global external Application Load Balancers. Don't use for: - Non-Google Cloud load balancing or security configurations. - Purely regional or internal load balancing setups (unless part of a hybrid/failover global design).

Ask your Agent

Use this Skill: https://skilld.dev/gh/google/skills/google-cloud-global-frontend-configuration

This session only. Nothing lands on disk.

referencesresource-discovery.md

≈437 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Google Cloud Resource Discovery Guidelines

This reference document details how to execute gcloud commands to discover and list existing Google Cloud resources (Cloud Storage buckets, Compute Engine Managed Instance Groups, GKE clusters, and Cloud Run services) in the project to assist with load balancer configuration.

Target Environment Assumptions

This resource discovery flow assumes it is executed in an environment (such as Gemini CLI, Antigravity, or a configured gLinux terminal) where the Google Cloud SDK (gcloud) is installed and has active credentials for the target project. If gcloud is not available, the agent must skip discovery and prompt the user to input their resource names manually.

Core Directives

  1. Discovery UX: Prioritize a clean, numbered-list UX for all resource discovery. Never ask for manual string input for existing resources. Always present lists starting with: 1. Create New, 2. NA.

  2. Project ID Detection: Auto-detect the target Google Cloud project ID using gcloud config get-value project.

  3. Resource Fetching Guidelines: When requested by the main configuration skill, fetch the specific resource types:

    • Google Cloud Storage Buckets: Run gcloud storage buckets list --format="value(name,location)"
    • Compute Engine Managed Instance Groups (MIGs): Run gcloud compute instance-groups managed list --format="value(name,region,zone)"
    • Cloud Run Services: Run gcloud run services list --format="value(name,region)"
    • (Only fetch the resource types that the user explicitly selected in their Origin Types.)

  4. Return Format: Return the discovered items clearly labeled with their region/zone where applicable.

Source: SKILL.md on GitHub

Third-party checks

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    This skill facilitates the design and deployment of Google Cloud infrastructure by guiding the configuration of Application Load Balancers. It includes considerations such as automated resource discovery and deployment script generation, which are standard practices for cloud infrastructure management. See the detailed analysis for context on these operations.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Provenance

Signed by skilld at becc4b8. 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 week

Capability

metadata
{
  "version": "1.0.0",
  "category": "Networking"
}

README badge

README badge for google/skills/google-cloud-global-frontend-configuration