Link updates - Fetch Google Cloud documentation as markdown instead of HTML

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
 <!-- disableFinding(LINE_OVER_80) -->
-[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).
 <!-- enableFinding(LINE_OVER_80) -->
 
 ```bash

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
 

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
 

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).

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).

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.

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).

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)
 

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
 

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)

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,24 +82,24 @@ 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
 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,24 +278,24 @@ 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
 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.

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)
 

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
 

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).

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
 

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
 

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)

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.
 

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)
+- [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)

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