From 16b3fef9905ca0adef1f97ea16bf0670cade9839 Mon Sep 17 00:00:00 2001 From: Cloud IX Team Date: Wed, 17 Jun 2026 13:34:02 -0700 Subject: [PATCH] Link updates - Fetch Google Cloud documentation as markdown instead of HTML PiperOrigin-RevId: 933895768 --- skills/cloud/agent-platform-tuning/SKILL.md | 2 +- .../references/models.md | 4 +- .../references/core-concepts.md | 2 +- .../alloydb-basics/references/iac-usage.md | 2 +- .../alloydb-basics/references/iam-security.md | 2 +- .../alloydb-basics/references/mcp-usage.md | 4 +- .../bigquery-basics/references/cli-usage.md | 2 +- .../references/client-library-usage.md | 6 +- .../references/iam-security.md | 2 +- .../bigquery-basics/references/mcp-usage.md | 6 +- skills/cloud/cloud-run-basics/SKILL.md | 28 ++++---- .../references/client-library-usage.md | 4 +- .../references/core-concepts.md | 12 ++-- .../cloud-run-basics/references/iac-usage.md | 2 +- .../references/iam-security.md | 2 +- .../cloud-run-basics/references/mcp-usage.md | 2 +- .../references/client-library-usage.md | 2 +- .../references/core-concepts.md | 2 +- .../references/iam-security.md | 6 +- .../cloud-sql-basics/references/mcp-usage.md | 6 +- skills/cloud/gcloud/SKILL.md | 6 +- skills/cloud/gemini-api/SKILL.md | 10 +-- .../gke-basics/references/gke-security.md | 2 +- .../cloud/gke-basics/references/mcp-usage.md | 2 +- .../cloud/google-cloud-recipe-auth/SKILL.md | 66 +++++++++---------- .../google-cloud-recipe-onboarding/SKILL.md | 16 ++--- .../SKILL.md | 8 +-- .../SKILL.md | 10 +-- .../SKILL.md | 8 +-- .../google-cloud-waf-reliability/SKILL.md | 18 ++--- .../cloud/google-cloud-waf-security/SKILL.md | 14 ++-- .../google-cloud-waf-sustainability/SKILL.md | 18 ++--- 32 files changed, 138 insertions(+), 138 deletions(-) diff --git a/skills/cloud/agent-platform-tuning/SKILL.md b/skills/cloud/agent-platform-tuning/SKILL.md index a3438d793a..b3d2018f4f 100644 --- a/skills/cloud/agent-platform-tuning/SKILL.md +++ b/skills/cloud/agent-platform-tuning/SKILL.md @@ -315,7 +315,7 @@ Check if `scripts/tune_gemini_model.py` exists. Submit the open model tuning job using `scripts/tune_open_model.py`. Identify the model id using available models documentation at -[documentation](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/open-model-tuning#supported-models). +[documentation](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/open-model-tuning.md.txt). ```bash diff --git a/skills/cloud/agent-platform-tuning/references/models.md b/skills/cloud/agent-platform-tuning/references/models.md index 542dcea298..464983e59b 100644 --- a/skills/cloud/agent-platform-tuning/references/models.md +++ b/skills/cloud/agent-platform-tuning/references/models.md @@ -12,10 +12,10 @@ Agent Platform. > Furthermore, do NOT recommend any model that is not explicitly listed in this > catalog, as the tuning service does not support it. -Available open models can be found in Google Cloud [documentation](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/open-model-tuning#supported-models). +Available open models can be found in Google Cloud [documentation](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/open-model-tuning.md.txt). This is the list of open models that are available for tuning; do not suggest any other open models besides the one listed here. -Each model has some [limitations](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/open-model-tuning#limitations) for tuning. +Each model has some [limitations](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/open-model-tuning.md.txt) for tuning. ## Model Selection Guidelines diff --git a/skills/cloud/alloydb-basics/references/core-concepts.md b/skills/cloud/alloydb-basics/references/core-concepts.md index 03403e517d..c4a3641ec2 100644 --- a/skills/cloud/alloydb-basics/references/core-concepts.md +++ b/skills/cloud/alloydb-basics/references/core-concepts.md @@ -8,7 +8,7 @@ allowing for efficient scaling and high availability. AlloyDB is ideal for enterprise-grade transactional workloads, such as ERP or CRM systems, as well as for analytical workloads that benefit from its columnar engine, and vector workloads using its [vector search -capabilities](https://docs.cloud.google.com/alloydb/docs/ai/perform-vector-search). +capabilities](https://docs.cloud.google.com/alloydb/docs/ai/perform-vector-search.md.txt). ## Regional Availability diff --git a/skills/cloud/alloydb-basics/references/iac-usage.md b/skills/cloud/alloydb-basics/references/iac-usage.md index 25b8ad5eab..149b96616c 100644 --- a/skills/cloud/alloydb-basics/references/iac-usage.md +++ b/skills/cloud/alloydb-basics/references/iac-usage.md @@ -132,4 +132,4 @@ spec: cpuCount: 2 ``` -For more information, see the [Config Connector resources](https://docs.cloud.google.com/config-connector/docs/reference/overview). +For more information, see the [Config Connector resources](https://docs.cloud.google.com/config-connector/docs/reference/overview.md.txt). diff --git a/skills/cloud/alloydb-basics/references/iam-security.md b/skills/cloud/alloydb-basics/references/iam-security.md index 5babc39cfc..a8f832f013 100644 --- a/skills/cloud/alloydb-basics/references/iam-security.md +++ b/skills/cloud/alloydb-basics/references/iam-security.md @@ -90,4 +90,4 @@ AlloyDB uses a managed service agent resources like storage and backups. Ensure this agent has the necessary permissions in your project. -For more information, see: [Security, privacy, risk, and compliance for AlloyDB for PostgreSQL](https://docs.cloud.google.com/alloydb/docs/security-privacy-compliance). +For more information, see: [Security, privacy, risk, and compliance for AlloyDB for PostgreSQL](https://docs.cloud.google.com/alloydb/docs/security-privacy-compliance.md.txt). diff --git a/skills/cloud/alloydb-basics/references/mcp-usage.md b/skills/cloud/alloydb-basics/references/mcp-usage.md index 0375abb984..3714427f15 100644 --- a/skills/cloud/alloydb-basics/references/mcp-usage.md +++ b/skills/cloud/alloydb-basics/references/mcp-usage.md @@ -22,8 +22,8 @@ server](https://cloud.google.com/alloydb/docs/ai/use-alloydb-mcp) guide. ## Resources -- [AlloyDB MCP Reference](https://cloud.google.com/alloydb/docs/reference/mcp) +- [AlloyDB MCP Reference](https://docs.cloud.google.com/alloydb/docs/reference/mcp.md.txt) - [MCP Toolbox](https://mcp-toolbox.dev/): An open-source alternative to the remote MCP server that runs on a local machine or IDE. - [MCP Toolbox AlloyDB Integration](https://mcp-toolbox.dev/integrations/alloydb/source/) - - [Configure your MCP client](https://docs.cloud.google.com/alloydb/docs/connect-ide-using-mcp-toolbox#configure-your-mcp-client) + - [Configure your MCP client](https://docs.cloud.google.com/alloydb/docs/connect-ide-using-mcp-toolbox.md.txt) - For additional specialized skills including health auditing, performance monitoring, and lifecycle management, install the [AlloyDB for PostgreSQL](https://github.com/gemini-cli-extensions/alloydb) Gemini CLI extension or Claude Plugin. diff --git a/skills/cloud/bigquery-basics/references/cli-usage.md b/skills/cloud/bigquery-basics/references/cli-usage.md index 3ed2a26f1f..b22bb049bd 100644 --- a/skills/cloud/bigquery-basics/references/cli-usage.md +++ b/skills/cloud/bigquery-basics/references/cli-usage.md @@ -108,4 +108,4 @@ bq COMMAND [FLAGS] [ARGUMENTS] - `--format`: Changes output format (e.g., `prettyjson`, `sparse`, `csv`). For the complete BigQuery CLI reference guide, visit: -[bq command-line tool reference](https://docs.cloud.google.com/bigquery/docs/reference/bq-cli-reference). +[bq command-line tool reference](https://docs.cloud.google.com/bigquery/docs/reference/bq-cli-reference.md.txt). diff --git a/skills/cloud/bigquery-basics/references/client-library-usage.md b/skills/cloud/bigquery-basics/references/client-library-usage.md index 512ff9950b..06ab80ba83 100644 --- a/skills/cloud/bigquery-basics/references/client-library-usage.md +++ b/skills/cloud/bigquery-basics/references/client-library-usage.md @@ -26,7 +26,7 @@ authenticated. results = query_job.result() ``` -- [Python Reference](https://docs.cloud.google.com/python/docs/reference/bigquery/latest) +- [Python Reference](https://docs.cloud.google.com/python/docs/reference/bigquery/latest.md.txt) ### Java @@ -48,7 +48,7 @@ authenticated. TableResult results = bigquery.query(queryConfig); ``` -- [Java Reference](https://docs.cloud.google.com/java/docs/reference/google-cloud-bigquery/latest/overview) +- [Java Reference](https://docs.cloud.google.com/java/docs/reference/google-cloud-bigquery/latest/overview.md.txt) ### Node.js (TypeScript) @@ -85,7 +85,7 @@ authenticated. it, _ := q.Read(ctx) ``` -- [Go Reference](https://docs.cloud.google.com/go/docs/reference/cloud.google.com/go/bigquery/latest) +- [Go Reference](https://docs.cloud.google.com/go/docs/reference/cloud.google.com/go/bigquery/latest.md.txt) ## BigQuery DataFrames (BigFrames) diff --git a/skills/cloud/bigquery-basics/references/iam-security.md b/skills/cloud/bigquery-basics/references/iam-security.md index 261ceef42b..3a234733f5 100644 --- a/skills/cloud/bigquery-basics/references/iam-security.md +++ b/skills/cloud/bigquery-basics/references/iam-security.md @@ -8,7 +8,7 @@ the most granular level—such as the table or view level—that is necessary. ## Predefined IAM Roles -For a complete list of predefined roles and detailed usage information, see [BigQuery IAM roles](https://docs.cloud.google.com/bigquery/docs/access-control#bigquery-roles). +For a complete list of predefined roles and detailed usage information, see [BigQuery IAM roles](https://docs.cloud.google.com/bigquery/docs/access-control.md.txt). ## Service Accounts and Agents diff --git a/skills/cloud/bigquery-basics/references/mcp-usage.md b/skills/cloud/bigquery-basics/references/mcp-usage.md index 30ae59255a..a1b97be408 100644 --- a/skills/cloud/bigquery-basics/references/mcp-usage.md +++ b/skills/cloud/bigquery-basics/references/mcp-usage.md @@ -22,7 +22,7 @@ charged to the project specified in the `project_id` field. ## Setup Instructions -To connect to the BigQuery MCP server, see [Configure a client connection](https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp#configure-client). +To connect to the BigQuery MCP server, see [Configure a client connection](https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp.md.txt). ## Supported Operations @@ -33,12 +33,12 @@ Agents using the BigQuery MCP remote server can perform tasks such as: - Getting table metadata. For more information about the BigQuery MCP server, visit: -[Use the BigQuery MCP server](https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp). +[Use the BigQuery MCP server](https://docs.cloud.google.com/bigquery/docs/use-bigquery-mcp.md.txt). Alternatively, you can use [MCP Toolbox](https://mcp-toolbox.dev/integrations/bigquery/source/), an open-source CLI tool that runs a local MCP server for BigQuery connections. For more on connecting BigQuery to your tools, see -[Connect LLMs to BigQuery with MCP](https://docs.cloud.google.com/bigquery/docs/pre-built-tools-with-mcp-toolbox) +[Connect LLMs to BigQuery with MCP](https://docs.cloud.google.com/bigquery/docs/pre-built-tools-with-mcp-toolbox.md.txt) for details. For additional specialized skills and advanced analytics workflows, install the [BigQuery Data Analytics extension](https://github.com/gemini-cli-extensions/bigquery-data-analytics) diff --git a/skills/cloud/cloud-run-basics/SKILL.md b/skills/cloud/cloud-run-basics/SKILL.md index 5c043760fd..b7da17165c 100644 --- a/skills/cloud/cloud-run-basics/SKILL.md +++ b/skills/cloud/cloud-run-basics/SKILL.md @@ -30,10 +30,10 @@ types: gcloud services enable run.googleapis.com cloudbuild.googleapis.com --quiet ``` -1. If you are under a domain restriction organization policy [restricting](https://docs.cloud.google.com/organization-policy/restrict-domains) +1. If you are under a domain restriction organization policy [restricting](https://docs.cloud.google.com/organization-policy/restrict-domains.md.txt) unauthenticated invocations for your project, you will need to access your deployed service as described under [Testing private - services](https://docs.cloud.google.com/run/docs/triggering/https-request#testing-private). + services](https://docs.cloud.google.com/run/docs/triggering/https-request.md.txt). ### Required roles @@ -82,16 +82,16 @@ Run instance is started. ### Supported container images You can directly use container images stored in the [Artifact -Registry](https://docs.cloud.google.com/artifact-registry/docs/overview), or +Registry](https://docs.cloud.google.com/artifact-registry/docs/overview.md.txt), or [Docker Hub](https://hub.docker.com/). Google recommends the use of Artifact Registry since Docker Hub images are -[cached](https://docs.cloud.google.com/artifact-registry/docs/pull-cached-dockerhub-images) +[cached](https://docs.cloud.google.com/artifact-registry/docs/pull-cached-dockerhub-images.md.txt) for up to one hour. You can use container images from other public or private registries (like JFrog Artifactory, Nexus, or GitHub Container Registry), by setting up an [Artifact Registry remote -repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo). +repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo.md.txt). You should only consider [Docker Hub](https://hub.docker.com/) for deploying popular container images such as [Docker Official @@ -99,7 +99,7 @@ Images](https://docs.docker.com/docker-hub/official_images/) or [Docker Sponsored OSS images](https://docs.docker.com/docker-hub/dsos-program/). For higher availability, Google recommends deploying these Docker Hub images using an [Artifact Registry remote -repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo). +repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo.md.txt). To deploy a container image, run the following command: @@ -147,7 +147,7 @@ There are two different ways to deploy your service from source: Cloud Run only supports automatic base images that use [Google Cloud's buildpacks base - images](https://docs.cloud.google.com/docs/buildpacks/base-images). + images](https://docs.cloud.google.com/docs/buildpacks/base-images.md.txt). * To deploy from source using a Dockerfile, run the following command: @@ -177,7 +177,7 @@ There are two different ways to deploy your service from source: * SERVICE_NAME: the name of your Cloud Run service. * APPLICATION_PATH: the location of your application on the local file system. - * BASE_IMAGE: the [runtime base image](https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images#how_to_obtain_base_images) + * BASE_IMAGE: the [runtime base image](https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images.md.txt) you want to use for your application. For example, `us-central1-docker.pkg.dev/serverless-runtimes/google-24-full/runtimes/nodejs24`. You can also deploy a pre-compiled binary without configuring additional @@ -189,7 +189,7 @@ There are two different ways to deploy your service from source: For examples on deploying from source without build, see [Examples of deploying from source without - build](https://docs.cloud.google.com/run/docs/deploying-source-code#examples-without-build). + build](https://docs.cloud.google.com/run/docs/deploying-source-code.md.txt). ## Create and execute a Cloud Run job @@ -278,16 +278,16 @@ digest (for example, ### Supported container images You can directly use container images stored in the [Artifact -Registry](https://docs.cloud.google.com/artifact-registry/docs/overview), or +Registry](https://docs.cloud.google.com/artifact-registry/docs/overview.md.txt), or [Docker Hub](https://hub.docker.com/). Google recommends the use of Artifact Registry since Docker Hub images are -[cached](https://docs.cloud.google.com/artifact-registry/docs/pull-cached-dockerhub-images) +[cached](https://docs.cloud.google.com/artifact-registry/docs/pull-cached-dockerhub-images.md.txt) for up to one hour. You can use container images from other public or private registries (like JFrog Artifactory, Nexus, or GitHub Container Registry), by setting up an [Artifact Registry remote -repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo). +repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo.md.txt). You should only consider [Docker Hub](https://hub.docker.com/) for deploying popular container images such as [Docker Official @@ -295,7 +295,7 @@ Images](https://docs.docker.com/docker-hub/official_images/) or [Docker Sponsored OSS images](https://docs.docker.com/docker-hub/dsos-program/). For higher availability, Google recommends deploying these Docker Hub images using an [Artifact Registry remote -repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo). +repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo.md.txt). To deploy a container image, run the following command: @@ -329,7 +329,7 @@ The deploy command defaults to source deployment if you don't supply the `--image` or `--source` flags. Behind the scenes, this command uses [Google Cloud's -buildpacks](https://docs.cloud.google.com/docs/buildpacks/overview) and Cloud +buildpacks](https://docs.cloud.google.com/docs/buildpacks/overview.md.txt) and Cloud Build to automatically build container images from your source code without having to install Docker on your machine or set up buildpacks or Cloud Build. By default, Cloud Run uses the default machine type provided by Cloud Build. diff --git a/skills/cloud/cloud-run-basics/references/client-library-usage.md b/skills/cloud/cloud-run-basics/references/client-library-usage.md index 1579b125ff..42dfb026df 100644 --- a/skills/cloud/cloud-run-basics/references/client-library-usage.md +++ b/skills/cloud/cloud-run-basics/references/client-library-usage.md @@ -27,7 +27,7 @@ Ensure you have the Google Cloud SDK installed and authenticated. page_result = client.list_services(request=request) ``` -- [Python Reference](https://docs.cloud.google.com/python/docs/reference/run/latest) +- [Python Reference](https://docs.cloud.google.com/python/docs/reference/run/latest.md.txt) ### Java @@ -64,7 +64,7 @@ Ensure you have the Google Cloud SDK installed and authenticated. } ``` -- [Java Reference](https://docs.cloud.google.com/java/docs/reference/google-cloud-run/latest/overview) +- [Java Reference](https://docs.cloud.google.com/java/docs/reference/google-cloud-run/latest/overview.md.txt) ### Node.js (TypeScript) diff --git a/skills/cloud/cloud-run-basics/references/core-concepts.md b/skills/cloud/cloud-run-basics/references/core-concepts.md index edfdb325b5..d3a3a9d083 100644 --- a/skills/cloud/cloud-run-basics/references/core-concepts.md +++ b/skills/cloud/cloud-run-basics/references/core-concepts.md @@ -61,7 +61,7 @@ Cloud Run services scale automatically based on: Your container image can run code written in the programming language of your choice and use any base image, provided that it respects the -constraints listed in the [Container runtime contract](https://docs.cloud.google.com/run/docs/container-contract). +constraints listed in the [Container runtime contract](https://docs.cloud.google.com/run/docs/container-contract.md.txt). Executables in the container image must be compiled for Linux 64-bit. Cloud Run specifically supports the Linux x86_64 ABI format. @@ -76,7 +76,7 @@ linux/amd64. For functions deployed with Cloud Run, you can use one of the Cloud Run runtime base images that are published by Google Cloud's buildpacks to receive automatic security and maintenance updates. -For more information about the supported runtimes, see the [Runtime support schedule](https://docs.cloud.google.com/run/docs/runtime-support). +For more information about the supported runtimes, see the [Runtime support schedule](https://docs.cloud.google.com/run/docs/runtime-support.md.txt). ### Container requirements @@ -106,7 +106,7 @@ deployment, each worker instance receives a private IP address on the configured network and subnet. Only resources from your VPC network can connect to the worker pool private IP address endpoint. For more information about obtaining the private IP addresses of your worker pool instance, see -[Retrieve the private IP addresses using the metadata server (MDS)](https://docs.cloud.google.com/run/docs/configuring/vpc-direct-vpc#mds-support). +[Retrieve the private IP addresses using the metadata server (MDS)](https://docs.cloud.google.com/run/docs/configuring/vpc-direct-vpc.md.txt). For Cloud Run worker pools with Direct VPC ingress, such as database connections or any other custom TCP-based protocol, the container must @@ -119,9 +119,9 @@ Cloud Run supports hosting AI inference models. You can configure services with GPUs (e.g., NVIDIA RTX PRO 6000 Blackwell GPU, NVIDIA L4) to accelerate workloads like LLM inference using Gemma 3. For more information, see GPU support for -[services](https://docs.cloud.google.com/run/docs/configuring/services/gpu), -[jobs](https://docs.cloud.google.com/run/docs/configuring/jobs/gpu), and [worker -pools](https://docs.cloud.google.com/run/docs/configuring/workerpools/gpu). +[services](https://docs.cloud.google.com/run/docs/configuring/services/gpu.md.txt), +[jobs](https://docs.cloud.google.com/run/docs/configuring/jobs/gpu.md.txt), and [worker +pools](https://docs.cloud.google.com/run/docs/configuring/workerpools/gpu.md.txt). ## Pricing diff --git a/skills/cloud/cloud-run-basics/references/iac-usage.md b/skills/cloud/cloud-run-basics/references/iac-usage.md index 32cd24642c..a9454a97ca 100644 --- a/skills/cloud/cloud-run-basics/references/iac-usage.md +++ b/skills/cloud/cloud-run-basics/references/iac-usage.md @@ -73,4 +73,4 @@ resource "google_cloud_run_v2_worker_pool" "default" { ## YAML Cloud Run resources can also be defined using YAML. For more information, see -[Cloud Run YAML reference](https://docs.cloud.google.com/run/docs/reference/yaml/v1). +[Cloud Run YAML reference](https://docs.cloud.google.com/run/docs/reference/yaml/v1.md.txt). diff --git a/skills/cloud/cloud-run-basics/references/iam-security.md b/skills/cloud/cloud-run-basics/references/iam-security.md index 5f974915bc..c00e097d8a 100644 --- a/skills/cloud/cloud-run-basics/references/iam-security.md +++ b/skills/cloud/cloud-run-basics/references/iam-security.md @@ -69,7 +69,7 @@ There are two ways to create a public Cloud Run service, you can either: * Assign the Cloud Run Invoker IAM role to the `allUsers` member type. For more information, see: -[Cloud Run security overview](https://docs.cloud.google.com/run/docs/securing/managing-access#make-service-public). +[Cloud Run security overview](https://docs.cloud.google.com/run/docs/securing/managing-access.md.txt). ## Configure IAP to secure access diff --git a/skills/cloud/cloud-run-basics/references/mcp-usage.md b/skills/cloud/cloud-run-basics/references/mcp-usage.md index abb2461755..41ded15534 100644 --- a/skills/cloud/cloud-run-basics/references/mcp-usage.md +++ b/skills/cloud/cloud-run-basics/references/mcp-usage.md @@ -30,7 +30,7 @@ To connect to the Cloud Run MCP server: 1. Enable the Cloud Run API in your Google Cloud project. 2. Configure the agent's MCP connection using the Gemini CLI extension. 3. Follow the setup guide: - [Setting up Cloud Run MCP](https://docs.cloud.google.com/run/docs/reference/mcp). + [Setting up Cloud Run MCP](https://docs.cloud.google.com/run/docs/reference/mcp.md.txt). ## Supported Operations diff --git a/skills/cloud/cloud-sql-basics/references/client-library-usage.md b/skills/cloud/cloud-sql-basics/references/client-library-usage.md index a853200eda..18c23d7cf6 100644 --- a/skills/cloud/cloud-sql-basics/references/client-library-usage.md +++ b/skills/cloud/cloud-sql-basics/references/client-library-usage.md @@ -113,4 +113,4 @@ certificates. To manage Cloud SQL resources (e.g., list instances) programmatically, use the `sqladmin` libraries. -- [Cloud SQL Admin API Overview](https://docs.cloud.google.com/sql/docs/mysql/admin-api) +- [Cloud SQL Admin API Overview](https://docs.cloud.google.com/sql/docs/mysql/admin-api.md.txt) diff --git a/skills/cloud/cloud-sql-basics/references/core-concepts.md b/skills/cloud/cloud-sql-basics/references/core-concepts.md index e6a3670f56..487d63a9f6 100644 --- a/skills/cloud/cloud-sql-basics/references/core-concepts.md +++ b/skills/cloud/cloud-sql-basics/references/core-concepts.md @@ -6,7 +6,7 @@ infrastructure while offering standard database engines. ## Supported Engines Cloud SQL supports the following database engines (see [supported -versions](https://docs.cloud.google.com/sql/docs/db-versions)): +versions](https://docs.cloud.google.com/sql/docs/db-versions.md.txt)): - **MySQL:** Versions 5.6, 5.7, 8.0, and 8.4. diff --git a/skills/cloud/cloud-sql-basics/references/iam-security.md b/skills/cloud/cloud-sql-basics/references/iam-security.md index 43c98e0920..60ce20d35b 100644 --- a/skills/cloud/cloud-sql-basics/references/iam-security.md +++ b/skills/cloud/cloud-sql-basics/references/iam-security.md @@ -62,6 +62,6 @@ a backup, nor clone, delete, or promote instances. Cannot start or stop Cloud Run or GKE) the `roles/cloudsql.client` role. For more information, see: -- [About Access Control - Cloud SQL for MySQL](https://docs.cloud.google.com/sql/docs/mysql/instance-access-control) -- [About Access Control - Cloud SQL for PostgreSQL](https://docs.cloud.google.com/sql/docs/postgres/instance-access-control) -- [About Access Control - Cloud SQL for SQL Server](https://docs.cloud.google.com/sql/docs/sqlserver/instance-access-control) \ No newline at end of file +- [About Access Control - Cloud SQL for MySQL](https://docs.cloud.google.com/sql/docs/mysql/instance-access-control.md.txt) +- [About Access Control - Cloud SQL for PostgreSQL](https://docs.cloud.google.com/sql/docs/postgres/instance-access-control.md.txt) +- [About Access Control - Cloud SQL for SQL Server](https://docs.cloud.google.com/sql/docs/sqlserver/instance-access-control.md.txt) \ No newline at end of file diff --git a/skills/cloud/cloud-sql-basics/references/mcp-usage.md b/skills/cloud/cloud-sql-basics/references/mcp-usage.md index 78c078b130..56f829985c 100644 --- a/skills/cloud/cloud-sql-basics/references/mcp-usage.md +++ b/skills/cloud/cloud-sql-basics/references/mcp-usage.md @@ -38,9 +38,9 @@ Plugin: Setup varies by database engine and whether you are connecting to a remote server or using the MCP Toolbox. For remote server setup, see Setting up -Cloud SQL MCP for [PostgreSQL](https://docs.cloud.google.com/sql/docs/postgres/use-cloudsql-mcp), -[MySQL](https://docs.cloud.google.com/sql/docs/mysql/use-cloudsql-mcp), or -[SQL Server](https://docs.cloud.google.com/sql/docs/sqlserver/use-cloudsql-mcp). +Cloud SQL MCP for [PostgreSQL](https://docs.cloud.google.com/sql/docs/postgres/use-cloudsql-mcp.md.txt), +[MySQL](https://docs.cloud.google.com/sql/docs/mysql/use-cloudsql-mcp.md.txt), or +[SQL Server](https://docs.cloud.google.com/sql/docs/sqlserver/use-cloudsql-mcp.md.txt). ## Supported Operations diff --git a/skills/cloud/gcloud/SKILL.md b/skills/cloud/gcloud/SKILL.md index 1e6ef89bc8..323b4dbb0c 100644 --- a/skills/cloud/gcloud/SKILL.md +++ b/skills/cloud/gcloud/SKILL.md @@ -22,7 +22,7 @@ argument syntax, prevent destructive actions, and minimize context window usage. ### 1. Installation If the `gcloud` executable is missing, refer to the official -[Google Cloud CLI Installation Guide](https://docs.cloud.google.com/sdk/docs/install-sdk) +[Google Cloud CLI Installation Guide](https://docs.cloud.google.com/sdk/docs/install-sdk.md.txt) to install it on your platform (Linux, macOS, Windows, etc.). ### 2. Authorization @@ -59,7 +59,7 @@ under the agent's focused identity. *(Impersonation requires For more detailed strategies and authentication types (such as Workload Identity Federation), see -[Authorizing the gcloud CLI](https://docs.cloud.google.com/sdk/docs/authorizing). +[Authorizing the gcloud CLI](https://docs.cloud.google.com/sdk/docs/authorizing.md.txt). ## Core Principles @@ -228,5 +228,5 @@ List Zones (GCE) | `gcloud compute zones list --project=` List Locations | `gcloud locations list --project=` Refer to the -[gcloud CLI Scripting Guide](https://docs.cloud.google.com/sdk/docs/scripting-gcloud) +[gcloud CLI Scripting Guide](https://docs.cloud.google.com/sdk/docs/scripting-gcloud.md.txt) for guidance on using the gcloud CLI in automation. diff --git a/skills/cloud/gemini-api/SKILL.md b/skills/cloud/gemini-api/SKILL.md index 6862f816f6..d7b4acb926 100644 --- a/skills/cloud/gemini-api/SKILL.md +++ b/skills/cloud/gemini-api/SKILL.md @@ -52,14 +52,14 @@ Provide these key capabilities: ``` > [!WARNING] -> Legacy SDKs like `google-cloud-aiplatform`, `@google-cloud/vertexai`, and `google-generativeai` are deprecated. Migrate to the new SDKs above urgently by following the [Migration Guide](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/deprecations/genai-vertexai-sdk). +> Legacy SDKs like `google-cloud-aiplatform`, `@google-cloud/vertexai`, and `google-generativeai` are deprecated. Migrate to the new SDKs above urgently by following the [Migration Guide](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/deprecations/genai-vertexai-sdk.md.txt). ## Authentication & Configuration Prefer environment variables over hard-coding parameters when creating the client. Initialize the client without parameters to automatically pick up these values. ### Application Default Credentials (ADC) -Set these variables for standard [Google Cloud authentication](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/start/gcp-auth): +Set these variables for standard [Google Cloud authentication](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/start/gcp-auth.md.txt): ```bash export GOOGLE_CLOUD_PROJECT='your-project-id' export GOOGLE_CLOUD_LOCATION='global' @@ -67,10 +67,10 @@ export GOOGLE_GENAI_USE_ENTERPRISE=true ``` - By default, use `location="global"` to access the global endpoint, which provides automatic routing to regions with available capacity. -- If a user explicitly asks to use a specific region (e.g., `us-central1`, `europe-west4`), specify that region in the `GOOGLE_CLOUD_LOCATION` parameter instead. Reference the [supported regions documentation](https://docs.cloud.google.com/gemini-enterprise-agent-platform/resources/locations#google-models) if needed. +- If a user explicitly asks to use a specific region (e.g., `us-central1`, `europe-west4`), specify that region in the `GOOGLE_CLOUD_LOCATION` parameter instead. Reference the [supported regions documentation](https://docs.cloud.google.com/gemini-enterprise-agent-platform/resources/locations.md.txt) if needed. ### Agent Platform in Express Mode -Set these variables when using [Express Mode](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/start/api-keys?usertype=expressmode) with an API key: +Set these variables when using [Express Mode](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/start/api-keys.md.txt) with an API key: ```bash export GOOGLE_API_KEY='your-api-key' export GOOGLE_GENAI_USE_ENTERPRISE=true @@ -213,7 +213,7 @@ Console.WriteLine(response.Text); When implementing or debugging API integration for Agent Platform, refer to the official Agent Platform documentation: - **Agent Platform Documentation**: https://docs.cloud.google.com/gemini-enterprise-agent-platform/overview.md.txt -- **REST API Reference**: https://docs.cloud.google.com/gemini-enterprise-agent-platform/reference/rest +- **REST API Reference**: https://docs.cloud.google.com/gemini-enterprise-agent-platform/reference/rest.md.txt The Gen AI SDK on Agent Platform uses the `v1beta1` or `v1` REST API endpoints (e.g., `https://{LOCATION}-aiplatform.googleapis.com/v1beta1/projects/{PROJECT}/locations/{LOCATION}/publishers/google/models/{MODEL}:generateContent`). diff --git a/skills/cloud/gke-basics/references/gke-security.md b/skills/cloud/gke-basics/references/gke-security.md index d4699ca5a6..4aed6d47df 100644 --- a/skills/cloud/gke-basics/references/gke-security.md +++ b/skills/cloud/gke-basics/references/gke-security.md @@ -99,7 +99,7 @@ gcloud container clusters describe --region \ - Audit permissions via MCP: `check_k8s_auth(parent="...", verb="list", resourceType="pods", namespace="...")` (or `kubectl auth can-i --list --as=`) - Review bindings via MCP: `get_k8s_resource(parent="...", resourceType="clusterrolebinding")` (or `kubectl get clusterrolebindings,rolebindings --all-namespaces`) -> See [gke-multitenancy.md](./gke-multitenancy.md) for enterprise RBAC planning and https://docs.cloud.google.com/kubernetes-engine/docs/best-practices/rbac +> See [gke-multitenancy.md](./gke-multitenancy.md) for enterprise RBAC planning and https://docs.cloud.google.com/kubernetes-engine/docs/best-practices/rbac.md.txt ## Binary Authorization diff --git a/skills/cloud/gke-basics/references/mcp-usage.md b/skills/cloud/gke-basics/references/mcp-usage.md index 66e6dbbf1a..97aa696be0 100644 --- a/skills/cloud/gke-basics/references/mcp-usage.md +++ b/skills/cloud/gke-basics/references/mcp-usage.md @@ -4,7 +4,7 @@ The GKE MCP server provides 23 structured tools for cluster management, Kubernet ## Connecting to the GKE MCP Server -The GKE remote MCP server is available for AI clients that support the Model Context Protocol. For setup instructions, see https://docs.cloud.google.com/kubernetes-engine/docs/how-to/use-gke-mcp. +The GKE remote MCP server is available for AI clients that support the Model Context Protocol. For setup instructions, see https://docs.cloud.google.com/kubernetes-engine/docs/how-to/use-gke-mcp.md.txt ## Available Tools diff --git a/skills/cloud/google-cloud-recipe-auth/SKILL.md b/skills/cloud/google-cloud-recipe-auth/SKILL.md index baaf341fd6..f8a0bb28e3 100644 --- a/skills/cloud/google-cloud-recipe-auth/SKILL.md +++ b/skills/cloud/google-cloud-recipe-auth/SKILL.md @@ -5,10 +5,10 @@ description: Provides expert guidance on authenticating and authorizing to Googl # Authenticating to Google Cloud -[Authentication](https://docs.cloud.google.com/docs/authentication) is the +[Authentication](https://docs.cloud.google.com/docs/authentication.md.txt) is the process of proving **who you are**. In Google Cloud, you represent a **Principal** (an identity like a user or a service). This is the first step -before [Authorization](https://docs.cloud.google.com/iam/docs/overview) +before [Authorization](https://docs.cloud.google.com/iam/docs/overview.md.txt) (determining **what you can do**). ## Authentication @@ -20,9 +20,9 @@ Before providing a specific solution, clarify the following with the user: 1. **Who or what is authenticating?** (A human developer, a local script, or an application running in production?) 2. **Where is the code running?** (Local laptop, [Compute - Engine](https://docs.cloud.google.com/compute/docs), - [GKE](https://docs.cloud.google.com/kubernetes-engine/docs), [Cloud - Run](https://docs.cloud.google.com/run/docs), or another cloud like + Engine](https://docs.cloud.google.com/compute/docs.md.txt), + [GKE](https://docs.cloud.google.com/kubernetes-engine/docs.md.txt), [Cloud + Run](https://docs.cloud.google.com/run/docs.md.txt), or another cloud like AWS/Azure?) 3. **What is the target?** (A Google Cloud API like Storage/BigQuery, or a custom application you built?) @@ -42,19 +42,19 @@ Google Cloud supports several ways to configure identities for your internal workforce (developers, administrators, employees): * **[Google-Managed - Accounts](https://docs.cloud.google.com/iam/docs/user-identities#google-accounts)**: + Accounts](https://docs.cloud.google.com/iam/docs/user-identities.md.txt)**: You can use Cloud Identity or Google Workspace to create managed user accounts. These are called managed accounts because your organization controls their lifecycle and configuration. * **[Federation using Cloud Identity or Google - Workspace](https://docs.cloud.google.com/iam/docs/user-identities#synced-federation)**: + Workspace](https://docs.cloud.google.com/iam/docs/user-identities.md.txt)**: You can federate identities to allow users to use their existing identity and credentials to sign in to Google services. Users authenticate against an external identity provider (IdP), but you must keep accounts synchronized into Google Cloud using tools like Google Cloud Directory Sync (GCDS) or an external authoritative source like Active Directory or Microsoft Entra ID. * **[Workforce Identity - Federation](https://docs.cloud.google.com/iam/docs/user-identities#workforce)**: + Federation](https://docs.cloud.google.com/iam/docs/user-identities.md.txt)**: This lets you use an external IdP to authenticate and authorize a workforce using IAM directly. Unlike standard federation, you do not need to synchronize user identities from your existing IdP to Google Cloud @@ -68,17 +68,17 @@ management. * **[Google Cloud Console](https://console.cloud.google.com/)**: The primary web interface. You authenticate using your Google Account (Gmail or [Google Workspace](https://workspace.google.com/)). -* **[gcloud CLI](https://docs.cloud.google.com/sdk/docs/install-sdk) (`gcloud +* **[gcloud CLI](https://docs.cloud.google.com/sdk/docs/install-sdk.md.txt) (`gcloud auth login`)**: Used to authenticate the CLI itself so you can run management commands (e.g., `gcloud compute instances list`). It uses a **Credential** (like an OAuth 2.0 refresh token) stored locally. * **Local Development with [App Default Credentials - (ADC)](https://docs.cloud.google.com/docs/authentication/application-default-credentials) + (ADC)](https://docs.cloud.google.com/docs/authentication/application-default-credentials.md.txt) (`gcloud auth application-default login`)**: This is different from CLI auth. It creates a local JSON file that Google Cloud **Client Libraries** (Python, Java, etc.) use to act as "you" when you run code on your laptop. * **[Service Account - Impersonation](https://docs.cloud.google.com/docs/authentication/use-service-account-impersonation)**: + Impersonation](https://docs.cloud.google.com/docs/authentication/use-service-account-impersonation.md.txt)**: For security reasons, developers should avoid downloading Service Account keys entirely. Instead, they should authenticate as humans (`gcloud auth login`) and use Service Account Impersonation to run CLI commands or @@ -91,14 +91,14 @@ Used when a human (who is not a developer) needs to access a web application you've deployed on Google Cloud. Note: These are distinct from workforce identities. -* **[Identity-Aware Proxy (IAP)](https://docs.cloud.google.com/iap/docs)**: +* **[Identity-Aware Proxy (IAP)](https://docs.cloud.google.com/iap/docs.md.txt)**: Acts as a central authorization layer for web applications. It intercepts web requests and verifies the user's identity (via Google Workspace, Cloud Identity, or external providers) before letting them reach the application. It's often used to protect internal apps without a VPN, or secure customer portals. * **[Identity - Platform](https://docs.cloud.google.com/identity-platform/docs)**: A + Platform](https://docs.cloud.google.com/identity-platform/docs.md.txt)**: A Customer Identity and Access Management (CIAM) solution for adding consumer sign-in (email/password, phone, social) directly into the code of your custom-built applications. @@ -113,10 +113,10 @@ human user account. ### Service Accounts and Service Agents * **[Service - Account](https://docs.cloud.google.com/iam/docs/service-account-overview)**: + Account](https://docs.cloud.google.com/iam/docs/service-account-overview.md.txt)**: A special identity intended for non-human users. It's like a "robot identity" with its own email address. -* **[Service Agent](https://docs.cloud.google.com/iam/docs/service-agents)**: +* **[Service Agent](https://docs.cloud.google.com/iam/docs/service-agents.md.txt)**: A service account managed by Google that allows a service (like Pub/Sub) to access your resources on your behalf. @@ -128,10 +128,10 @@ environment then provides a **Token** (a short-lived digital object) via a local metadata server. * **[Compute - Engine](https://docs.cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances)**: + Engine](https://docs.cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances.md.txt)**: Assign a service account during VM creation. * **[Cloud - Run](https://docs.cloud.google.com/run/docs/securing/service-identity)**: + Run](https://docs.cloud.google.com/run/docs/securing/service-identity.md.txt)**: Assign a service account in the service configuration. ### Special Cases & Advanced Topics @@ -139,31 +139,31 @@ metadata server. #### Kubernetes Engine (GKE) Use **[Workload Identity Federation for -GKE](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/workload-identity)** +GKE](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.md.txt)** to map Kubernetes identities to IAM principal identifiers. This grants specific Kubernetes workloads access to specific Google Cloud APIs. [Learn more -here.](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#configure-authz-principals) +here.](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.md.txt) -#### External Workloads ([Workload Identity Federation](https://docs.cloud.google.com/iam/docs/workload-identity-federation)) +#### External Workloads ([Workload Identity Federation](https://docs.cloud.google.com/iam/docs/workload-identity-federation.md.txt)) For code running **outside** Google Cloud (e.g., AWS, Azure, or on-prem), do not use keys. Instead, use Workload Identity Federation to exchange an external token (like an AWS IAM role) for a short-lived Google Cloud access token. -#### [API Keys](https://docs.cloud.google.com/docs/authentication/api-keys) +#### [API Keys](https://docs.cloud.google.com/docs/authentication/api-keys.md.txt) API keys are encrypted strings used for public data (e.g., Google Maps) or simplified access like **[Vertex AI Express -Mode](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/start/express-mode/overview)**, +Mode](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/start/express-mode/overview.md.txt)**, which allows fast testing of Gemini models without complex setup. Both humans and services (e.g., Cloud Run-based AI agent) can use API keys, for the services that support it. Note: API keys should be -[restricted](https://docs.cloud.google.com/api-keys/docs/add-restrictions-api-keys) +[restricted](https://docs.cloud.google.com/api-keys/docs/add-restrictions-api-keys.md.txt) to specific APIs and projects to minimize security risks. Store API keys in a secrets manager like [Secret -Manager](https://docs.cloud.google.com/secret-manager/docs) to prevent +Manager](https://docs.cloud.google.com/secret-manager/docs.md.txt) to prevent accidental exposure. #### OAuth 2.0 Access Scopes @@ -186,17 +186,17 @@ Web Tokens (JWTs) dynamically, removing the need for static credentials. ## Authorization After Authentication, Google Cloud uses **[Identity and Access Management -(IAM)](https://docs.cloud.google.com/iam/docs/overview)** to determine what the +(IAM)](https://docs.cloud.google.com/iam/docs/overview.md.txt)** to determine what the authenticated principal can do. * **Allow Policy**: A record that binds a **Principal** to a **Role** on a **Resource**. * **[Predefined - Roles](https://docs.cloud.google.com/iam/docs/understanding-roles)**: + Roles](https://docs.cloud.google.com/iam/docs/roles-permissions)**: Prebuilt roles like `roles/storage.objectViewer` or `roles/bigquery.dataEditor`. **Always try to use these first.** * **[Custom - Roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles)**: + Roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles.md.txt)**: User-defined collections of specific permissions if predefined roles are too broad. @@ -224,7 +224,7 @@ authenticated principal can do. 3. **Code**: The Cloud Run environment provides the token automatically to the connection driver. -### Calling a Custom Application ([OIDC](https://docs.cloud.google.com/docs/authentication/get-id-token)) +### Calling a Custom Application ([OIDC](https://docs.cloud.google.com/docs/authentication/get-id-token.md.txt)) When calling a private Cloud Run service from another service, the caller generates a Google-signed **OpenID Connect (OIDC) ID Token** and passes it in @@ -246,13 +246,13 @@ the `Authorization: Bearer ` header. Federation. - [ ] Is the user calling a custom app? Recommend OIDC ID Tokens. - [ ] Has the user restricted their API Keys? Check for appropriate [API Key - Restrictions](https://docs.cloud.google.com/docs/authentication/api-keys#adding-application-restrictions). + Restrictions](https://docs.cloud.google.com/docs/authentication/api-keys.md.txt). ## References -- [Authentication Overview](https://docs.cloud.google.com/docs/authentication) -- [User Identities](https://docs.cloud.google.com/iam/docs/user-identities) -- [Application Default Credentials](https://docs.cloud.google.com/docs/authentication/provide-credentials-adc) -- [Service Account Best Practices](https://docs.cloud.google.com/iam/docs/best-practices-service-accounts) +- [Authentication Overview](https://docs.cloud.google.com/docs/authentication.md.txt) +- [User Identities](https://docs.cloud.google.com/iam/docs/user-identities.md.txt) +- [Application Default Credentials](https://docs.cloud.google.com/docs/authentication/provide-credentials-adc.md.txt) +- [Service Account Best Practices](https://docs.cloud.google.com/iam/docs/best-practices-service-accounts.md.txt) diff --git a/skills/cloud/google-cloud-recipe-onboarding/SKILL.md b/skills/cloud/google-cloud-recipe-onboarding/SKILL.md index 91cb173e3b..afaf311b43 100644 --- a/skills/cloud/google-cloud-recipe-onboarding/SKILL.md +++ b/skills/cloud/google-cloud-recipe-onboarding/SKILL.md @@ -27,7 +27,7 @@ This skill provides a streamlined, non-interactive "happy path" for a singleton ## Overview -For an individual developer, onboarding to Google Cloud involves verifying local terminal tools, establishing an authenticated session, selecting or instantiating a workspace ([Project](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy#projects)), and linking it to an active billing account. Google Cloud offers a Free Tier and a Free Trial with $300 in credits for first-time users. [Learn more here](https://docs.cloud.google.com/free/docs/free-cloud-features). +For an individual developer, onboarding to Google Cloud involves verifying local terminal tools, establishing an authenticated session, selecting or instantiating a workspace ([Project](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy.md.txt)), and linking it to an active billing account. Google Cloud offers a Free Tier and a Free Trial with $300 in credits for first-time users. [Learn more here](https://docs.cloud.google.com/free/docs/free-cloud-features). --- @@ -53,7 +53,7 @@ Before soliciting input or proposing mutations, silently audit the host system's gcloud auth list --format="json" ``` 3. If the pre-execution audit for `which gcloud` returns a valid path, proceed directly to Section 2: Authenticate and Route Session. -4. If the binary is missing, halt execution and direct the agent/developer to the [gcloud skill](https://github.com/google/skills/tree/main/skills/cloud/gcloud) or official [Google Cloud CLI Installation Guide](https://docs.cloud.google.com/sdk/docs/install) for setup and authentication instructions before retrying. +4. If the binary is missing, halt execution and direct the agent/developer to the [gcloud skill](https://github.com/google/skills/tree/main/skills/cloud/gcloud) or official [Google Cloud CLI Installation Guide](https://docs.cloud.google.com/sdk/docs/install-sdk.md.txt) for setup and authentication instructions before retrying. --- @@ -85,7 +85,7 @@ Authorize the gcloud CLI to access Google Cloud using the developer's Google Acc - Note that new Free Trial accounts automatically receive a Self-Owned Organization (SOO). To distinguish between a personal Free Trial account and an enterprise organization, inspect the JSON output: - **Enterprise Organization (Halt Execution)**: If the output list contains an organization node where `owner.directoryCustomerId` is present (confirming a domain-verified Google Workspace or Cloud Identity organization), or if the user's prompt explicitly mentions corporate landing zones or multi-tenant project structures: - **Halt execution** of this skill immediately. - - Route the developer to the official [Google Cloud Setup guided flow](https://docs.cloud.google.com/docs/enterprise/cloud-setup). + - Route the developer to the official [Google Cloud Setup guided flow](https://docs.cloud.google.com/docs/enterprise/cloud-setup.md.txt). - **Personal Account / Free Trial SOO (Proceed)**: If the output list is empty `[]`, or if it contains a Self-Owned Organization (where `owner.directoryCustomerId` is absent and `displayName` is not a verified domain name), proceed to Section 3: Select or Instantiate Your Google Cloud Project. --- @@ -163,9 +163,9 @@ Onboarding setup is now complete. To safeguard your environment and deploy workl 1. **Billing Spend Controls:** To avoid accidental cost overruns, consider setting up a programmatic control to automatically disable billing. When billing is disabled, all Google Cloud services and usage in the project are terminated to stop further costs: - - Direct the developer to the official [Disable Billing Usage with Notifications Guide](https://docs.cloud.google.com/billing/docs/how-to/disable-billing-with-notifications), which provides detailed instructions on how to automatically shut down billing when costs exceed the project budget. + - Direct the developer to the official [Disable Billing Usage with Notifications Guide](https://docs.cloud.google.com/billing/docs/how-to/disable-billing-with-notifications.md.txt), which provides detailed instructions on how to automatically shut down billing when costs exceed the project budget. 2. **Deploy Workloads:** - To deploy your first resource, trigger the downstream specialized skill matching your target application (e.g., [cloud-run-basics](https://github.com/google/skills/blob/main/skills/cloud/cloud-run-basics) or `bigquery-basics`). If the specialized skill is not locally available, direct the developer to the corresponding official quickstart, such as the [Cloud Run Container Deployment Quickstart](https://docs.cloud.google.com/run/docs/quickstarts/deploy-container). + To deploy your first resource, trigger the downstream specialized skill matching your target application (e.g., [cloud-run-basics](https://github.com/google/skills/blob/main/skills/cloud/cloud-run-basics) or `bigquery-basics`). If the specialized skill is not locally available, direct the developer to the corresponding official quickstart, such as the [Cloud Run Container Deployment Quickstart](https://docs.cloud.google.com/run/docs/quickstarts/deploy-container.md.txt). *Note: Those downstream specialized skills are individually responsible for dynamically enabling their own required service APIs (e.g., run.googleapis.com) inline during execution.* --- @@ -195,8 +195,8 @@ After completing the onboarding steps, programmatically verify the completed env ## Additional Resources -- [Google Cloud Getting Started landing page](https://docs.cloud.google.com/docs/get-started) -- [Google Cloud overview](https://docs.cloud.google.com/docs/overview) +- [Google Cloud Getting Started landing page](https://docs.cloud.google.com/docs/get-started.md.txt) +- [Google Cloud overview](https://docs.cloud.google.com/docs/overview.md.txt) - [Google Cloud Free Program](https://docs.cloud.google.com/free/docs/free-cloud-features) -- [Google Cloud Cloud Setup guided flow](https://docs.cloud.google.com/docs/enterprise/cloud-setup) +- [Google Cloud Cloud Setup guided flow](https://docs.cloud.google.com/docs/enterprise/cloud-setup.md.txt) diff --git a/skills/cloud/google-cloud-waf-cost-optimization/SKILL.md b/skills/cloud/google-cloud-waf-cost-optimization/SKILL.md index 8c92f55faa..669dab15d9 100644 --- a/skills/cloud/google-cloud-waf-cost-optimization/SKILL.md +++ b/skills/cloud/google-cloud-waf-cost-optimization/SKILL.md @@ -23,25 +23,25 @@ Framework are aligned with the following core principles: business objectives. Prioritize investments that directly contribute to revenue, customer satisfaction, or operational efficiency. Grounding document: - https://docs.cloud.google.com/architecture/framework/cost-optimization/align-cloud-spending-business-value + https://docs.cloud.google.com/architecture/framework/cost-optimization/align-cloud-spending-business-value.md.txt - **Foster a culture of cost awareness**: Ensure that people across your organization consider the cost impact of their decisions and activities. Provide teams with the visibility and information they need to make informed, cost-conscious choices. Grounding document: - https://docs.cloud.google.com/architecture/framework/cost-optimization/foster-culture-cost-awareness + https://docs.cloud.google.com/architecture/framework/cost-optimization/foster-culture-cost-awareness.md.txt - **Optimize resource usage**: Provision only the resources that you need and pay only for what you consume. Select the most cost-effective resource types, sizes, and locations that meet your technical and business requirements. Grounding document: - https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-resource-usage + https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-resource-usage.md.txt - **Optimize continuously**: Continuously monitor your cloud resource usage and costs, and proactively make adjustments as needed to optimize your spending. This iterative approach helps identify and address inefficiencies before they become significant. Grounding document: - https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-continuously + https://docs.cloud.google.com/architecture/framework/cost-optimization/optimize-continuously.md.txt ## Relevant Google Cloud products diff --git a/skills/cloud/google-cloud-waf-operational-excellence/SKILL.md b/skills/cloud/google-cloud-waf-operational-excellence/SKILL.md index 0606adc663..5eaab2fbeb 100644 --- a/skills/cloud/google-cloud-waf-operational-excellence/SKILL.md +++ b/skills/cloud/google-cloud-waf-operational-excellence/SKILL.md @@ -27,27 +27,27 @@ Framework are aligned with the following core principles: - **Ensure operational readiness**: Define and measure criteria for a workload to be considered ready for production, including staffing, processes, and governance. Grounding document: - https://docs.cloud.google.com/architecture/framework/operational-excellence/operational-readiness-and-performance-using-cloudops + https://docs.cloud.google.com/architecture/framework/operational-excellence/operational-readiness-and-performance-using-cloudops.md.txt - **Manage incidents and problems**: Establish structured processes for incident response, communication, and root cause analysis to minimize impact and prevent recurrence. Grounding document: - https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-incidents-and-problems + https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-incidents-and-problems.md.txt - **Manage and optimize cloud resources**: Monitor resource utilization and right-size environments to maintain performance while ensuring operational efficiency. Grounding document: - https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-and-optimize-cloud-resources + https://docs.cloud.google.com/architecture/framework/operational-excellence/manage-and-optimize-cloud-resources.md.txt - **Automate and manage change**: Use Infrastructure as Code (IaC) and CI/CD pipelines to ensure consistent, repeatable, and low-risk deployments and configuration changes. Grounding document: - https://docs.cloud.google.com/architecture/framework/operational-excellence/automate-and-manage-change + https://docs.cloud.google.com/architecture/framework/operational-excellence/automate-and-manage-change.md.txt - **Continuously improve and innovate**: Regularly review architectures, monitor industry trends, and adapt operations to meet evolving business needs. Grounding document: - https://docs.cloud.google.com/architecture/framework/operational-excellence/continuously-improve-and-innovate + https://docs.cloud.google.com/architecture/framework/operational-excellence/continuously-improve-and-innovate.md.txt ## Relevant Google Cloud products diff --git a/skills/cloud/google-cloud-waf-performance-optimization/SKILL.md b/skills/cloud/google-cloud-waf-performance-optimization/SKILL.md index 8500d11b7a..c2dfeb100d 100644 --- a/skills/cloud/google-cloud-waf-performance-optimization/SKILL.md +++ b/skills/cloud/google-cloud-waf-performance-optimization/SKILL.md @@ -27,23 +27,23 @@ Well-Architected Framework are aligned with the following core principles: - **Plan resource allocation**: Carefully select and configure the compute, storage, and networking resources that best match the specific requirements of your workload. Grounding document: - https://docs.cloud.google.com/architecture/framework/performance-optimization/plan-resource-allocation + https://docs.cloud.google.com/architecture/framework/performance-optimization/plan-resource-allocation.md.txt - **Take advantage of elasticity**: Utilize automated scaling and serverless technologies to dynamically adjust resource capacity in response to real-time demand fluctuations. Grounding document: - https://docs.cloud.google.com/architecture/framework/performance-optimization/elasticity + https://docs.cloud.google.com/architecture/framework/performance-optimization/elasticity.md.txt - **Promote modular design**: Architect systems using independent, loosely coupled components to enhance scalability and allow individual parts to be optimized without affecting the entire system. Grounding document: - https://docs.cloud.google.com/architecture/framework/performance-optimization/promote-modular-design + https://docs.cloud.google.com/architecture/framework/performance-optimization/promote-modular-design.md.txt - **Continuously monitor and improve performance**: Implement robust observability to identify bottlenecks and use performance data to drive iterative enhancements throughout the software development lifecycle. Grounding document: - https://docs.cloud.google.com/architecture/framework/performance-optimization/continuously-monitor-and-improve-performance + https://docs.cloud.google.com/architecture/framework/performance-optimization/continuously-monitor-and-improve-performance.md.txt ## Relevant Google Cloud products diff --git a/skills/cloud/google-cloud-waf-reliability/SKILL.md b/skills/cloud/google-cloud-waf-reliability/SKILL.md index fd019fc5cb..9616063c46 100644 --- a/skills/cloud/google-cloud-waf-reliability/SKILL.md +++ b/skills/cloud/google-cloud-waf-reliability/SKILL.md @@ -23,52 +23,52 @@ are aligned with the following core principles: 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 + https://docs.cloud.google.com/architecture/framework/reliability/define-reliability-based-on-user-experience-goals.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/set-targets.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/build-highly-available-systems.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/horizontal-scalability.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/observability.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/graceful-degradation.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-data-loss.md.txt - **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 + https://docs.cloud.google.com/architecture/framework/reliability/conduct-postmortems.md.txt ## Relevant Google Cloud products diff --git a/skills/cloud/google-cloud-waf-security/SKILL.md b/skills/cloud/google-cloud-waf-security/SKILL.md index b95840c970..1f76ee650b 100644 --- a/skills/cloud/google-cloud-waf-security/SKILL.md +++ b/skills/cloud/google-cloud-waf-security/SKILL.md @@ -25,13 +25,13 @@ aligned with the following core principles: applications and infrastructure. Google Cloud provides architecture blueprints and recommendations to help you apply this principle. Grounding document: - https://docs.cloud.google.com/architecture/framework/security/implement-security-by-design + https://docs.cloud.google.com/architecture/framework/security/implement-security-by-design.md.txt - **Implement zero trust**: Use a _never trust, always verify_ approach, where access to resources is granted based on continuous verification of trust. Google Cloud supports this principle through products like Chrome Enterprise Premium and Identity-Aware Proxy (IAP). Grounding document: - https://docs.cloud.google.com/architecture/framework/security/implement-zero-trust + https://docs.cloud.google.com/architecture/framework/security/implement-zero-trust.md.txt - **Implement shift-left security**: Implement security controls early in the software development lifecycle. Avoid security defects before system changes @@ -39,7 +39,7 @@ aligned with the following core principles: system changes are committed. Google Cloud supports this principle through products like Cloud Build, Binary Authorization, and Artifact Registry. Grounding document: - https://docs.cloud.google.com/architecture/framework/security/implement-shift-left-security + https://docs.cloud.google.com/architecture/framework/security/implement-shift-left-security.md.txt - **Implement preemptive cyber defense**: Adopt a proactive approach to security by implementing robust fundamental measures like threat @@ -48,13 +48,13 @@ aligned with the following core principles: controls aligns with this principle. Google Cloud supports this principle through products like Security Command Center, Google Threat Intelligence, and Google SecOps. Grounding document: - https://docs.cloud.google.com/architecture/framework/security/implement-preemptive-cyber-defense + https://docs.cloud.google.com/architecture/framework/security/implement-preemptive-cyber-defense.md.txt - **Use AI securely and responsibly**: Develop and deploy AI systems in a responsible and secure manner. The recommendations for this principle are aligned with guidance in the AI and ML perspective of the Well-Architected Framework and in Google's Secure AI Framework (SAIF). Grounding document: - https://docs.cloud.google.com/architecture/framework/security/use-ai-securely-and-responsibly + https://docs.cloud.google.com/architecture/framework/security/use-ai-securely-and-responsibly.md.txt - **Use AI for security**: Use AI capabilities to improve your existing security systems and processes through Gemini in Security and overall @@ -62,14 +62,14 @@ aligned with the following core principles: of remedial work and ensure security hygiene to make other systems more secure. Google Cloud supports this principle through products like Google Threat Intelligence and Google SecOps. Grounding document: - https://docs.cloud.google.com/architecture/framework/security/use-ai-for-security + https://docs.cloud.google.com/architecture/framework/security/use-ai-for-security.md.txt - **Meet regulatory, compliance, and privacy needs**: Adhere to industry-specific regulations, compliance standards, and privacy requirements. Google Cloud helps you meet these obligations through products like Assured Workloads, Organization Policy Service, and our compliance resource center. Grounding document: - https://docs.cloud.google.com/architecture/framework/security/meet-regulatory-compliance-and-privacy-needs + https://docs.cloud.google.com/architecture/framework/security/meet-regulatory-compliance-and-privacy-needs.md.txt ## Relevant Google Cloud products diff --git a/skills/cloud/google-cloud-waf-sustainability/SKILL.md b/skills/cloud/google-cloud-waf-sustainability/SKILL.md index 69ae6e6278..840e5c5696 100644 --- a/skills/cloud/google-cloud-waf-sustainability/SKILL.md +++ b/skills/cloud/google-cloud-waf-sustainability/SKILL.md @@ -29,53 +29,53 @@ Framework are aligned with the following core principles: embrace a shared fate model, working with your cloud provider and partners to achieve optimal environmental outcomes for the entire ecosystem. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability#shared-responsibility + https://docs.cloud.google.com/architecture/framework/sustainability.md.txt - **Use regions that consume low-carbon energy**: Prioritize Google Cloud regions with a high percentage of Carbon-Free Energy (CFE) and "Low CO2" indicators to lower the gross carbon emissions of your deployments. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/low-carbon-regions + https://docs.cloud.google.com/architecture/framework/sustainability/low-carbon-regions.md.txt - **Optimize AI and ML workloads**: Maximize computations per watt by matching algorithmic needs to specialized hardware (like TPUs) and applying mathematical techniques to reduce computational complexity. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/ai-ml-energy-efficiency + https://docs.cloud.google.com/architecture/framework/sustainability/ai-ml-energy-efficiency.md.txt - **Optimize resource usage**: Eliminate energy waste by scaling resources to zero when idle, rightsizing virtual machines, and prioritizing managed services that dynamically match actual demand. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/optimize-resource-usage + https://docs.cloud.google.com/architecture/framework/sustainability/optimize-resource-usage.md.txt - **Develop energy-efficient software**: Design your applications to minimize unnecessary CPU, memory, and network activity on both backend servers and end-user devices by using event-driven logic and optimized assets. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/energy-efficient-software + https://docs.cloud.google.com/architecture/framework/sustainability/energy-efficient-software.md.txt - **Optimize data and storage**: Reduce the environmental footprint of your storage by implementing lifecycle management to archive cold data and eliminating "dark data" that provides no business value. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/optimize-storage + https://docs.cloud.google.com/architecture/framework/sustainability/optimize-storage.md.txt - **Continuously measure and improve**: Gain visibility into your carbon emissions by analyzing granular data, identifying hotspots, and taking proactive steps to remediate inefficiencies. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/continuously-measure-improve + https://docs.cloud.google.com/architecture/framework/sustainability/continuously-measure-improve.md.txt - **Promote a culture of sustainability**: Embed sustainability into your organizational governance, connect technical decisions to environmental goals, and ensure staff have the skills to implement green practices. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/culture + https://docs.cloud.google.com/architecture/framework/sustainability/culture.md.txt - **Align sustainability practices with industry guidelines**: Ensure that your sustainability initiatives are aligned with industry guidelines for measurement, reporting, and verification, such as W3C Web Sustainability Guidelines, Green Software Foundation, and Greenhouse Gas Protocol. Grounding document: - https://docs.cloud.google.com/architecture/framework/sustainability/industry-guidelines + https://docs.cloud.google.com/architecture/framework/sustainability/industry-guidelines.md.txt ## Relevant Google Cloud products