gcloud CLI Skill for AI Agents
[!CAUTION]
MANDATORY PRE-CONDITION: EXPLICIT LEAF-LEVEL SYNTAX VALIDATION
All pre-existing knowledge of gcloud commands, flags, flag values, and
positional argument syntax is stale and prone to hallucination.
NEVER propose command parameters, output flag options, execute commands, OR
outline step-by-step plans for any gcloud task before validating leaf-level
syntax via gcloud help <command> (or including leaf-level help lookup as a
mandatory step in the plan).
Mandatory Action Rules:
Direct Execution & Code Generation: ALWAYS invoke gcloud help <leaf_command> (e.g. gcloud help compute instances create or gcloud help sql instances create) before proposing or executing the final
command syntax, UNLESS the user prompt already provides gcloud help
output, states to assume command syntax is already validated, or instructs
not to execute any commands. When instructed not to execute any commands,
NEVER invoke run_command (not even for gcloud help or directory
listing commands like ls); read bundled reference files
(references/cli-usage.md, references/mcp-usage.md, and
references/attribution.md) directly with read_file.
Planning & Strategy Queries: When asked for a plan, strategy, or next
steps to achieve a user goal (e.g., "What is your plan to accomplish
X..."), the response MUST explicitly include running gcloud help <leaf_command> as Step 1 of the plan before proposing flags or
executing commands.
Non-Transitive Validation: Parent command group help (e.g. gcloud help compute) is not sufficient for leaf-level syntax validation.
Validation must occur at the specific leaf subcommand level.
FORBIDDEN Web Search Fallback: NEVER use search_web, web search, or
external documentation search tools for gcloud CLI syntax. gcloud help <leaf_command> is the EXCLUSIVE authorized authority for command
syntax.
User Flag & Project Preservation: When proposing intermediate command
steps, ALWAYS preserve all user-specified flags (including
--project=<project_id>) in the proposed response text.
Mandatory Plan Template: When generating a plan, the response MUST
copy this exact 4-step structure:
- Step 1: Syntax Validation via
gcloud help <leaf_command>
- Step 2: Parameter Verification (confirming required and optional
flags, and explicitly checking if the
--dry-run or --validate-only
flag is supported)
- Step 3: Dry-Run Command Proposal (If
--dry-run or
--validate-only is supported, there MUST be a --dry-run or
--validate-only invocation before the next step.)
- Step 4: Command Proposal & Authorization (If the command is on the
"Prohibited Operations" denylist, state that autonomous execution is
forbidden, and the user MUST be explicitly asked for authorization to
proceed. If the command is NOT on the denylist, propose or proceed
with execution, while following ALL "Execution Constraints" below.)
This document provides essential guidelines and best practices for AI agents
interacting with the Google Cloud SDK (gcloud CLI). Following these rules is
critical to avoid hallucinated commands, flags, flag values, and positional
argument syntax, prevent destructive actions, and minimize context window usage.
Usage Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read and follow the instructions in
Usage Attribution. If a more specific product or
domain skill (e.g., cloud-run-basics, bigquery-basics, gke-basics) is
also loaded or active for the current task, ALWAYS use that specific
skill's skill:<name> attribution tag instead of skill:gcloud. For commands
executed directly in the terminal when no product-specific skill applies (never
in generated scripts, Terraform, or user code), prefix gcloud with
CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:gcloud)"
and append agent-skills/1.0 (skill:gcloud) to User-Agent headers.
Execution Modes
AI agents can interact with Google Cloud resources in two primary ways:
- Direct CLI Execution: Executing
gcloud commands directly in a local or
automated shell environment. See CLI Usage for
installation, authentication flows, and configuration management.
- Model Context Protocol (MCP): Invoking structured tools via the Cloud
CLI remote MCP server (
run_gcloud_command). See
MCP Usage for tool schemas, parameter rules, and
server configuration.
Core Principles
1. Explicit Command Validation (Mandatory)
- Action: ALWAYS call
gcloud help <command> for the exact command
that is intended to be run (e.g., gcloud help compute instances create).
- Verify: Ensure the command, flags, flag values, and positional argument
syntax are valid for that specific leaf command before attempting execution
or presenting plans. Validation is not transitive from parent groups.
2. Data Reduction Strategies (Mandatory)
Minimize the volume of data returned by gcloud to save context window space
and reduce latency. DO NOT execute any list command without including at least
one data reduction flag (--limit, --filter, or --format).
Projection: Use --format="json(key1, key2, ...)" to select only the
specific fields needed for the task. To understand the advanced projection
and formatting syntax, refer to gcloud topic projections and gcloud topic formats.
Limiting: Use --limit=N to cap the number of resources returned.
Filtering: Use --filter to narrow down results server-side. Prioritize
: for pattern matching and never quote the right side of the colon. Treat
the entire filter flag as a singular string without quoting or escaping
characters. To study the filter expression syntax, refer to gcloud topic filters.
Schema Discovery: Unconstrained resource lists can quickly exhaust the
context window with redundant data. To prevent this, discover a resource's
schema before executing queries. If unsure of the JSON key path for
projecting fields (--format) or filtering (--filter), run the targeted
resource's list command (if supported) with a single-item limit:
gcloud <GROUP> <RESOURCE> list --limit=1 --format=json
Examine this single instance's JSON structure to safely identify the correct
schema keys before requesting full or filtered datasets.
3. Execution Constraints
- Single Commands: Execute a single
gcloud command at a time. No command
chaining or sequencing.
- No Shell Operators: Do not use command substitution (
$(...)), pipes
(|), or redirection (>, >>, <). This is to increase command safety
and ensure commands are more easily understandable and reviewable by users.
- Non-Interactive Execution (
--quiet / -q): Pass the --quiet (or
-q) global flag on all execution commands (e.g., gcloud pubsub topics delete temp-topic --quiet --project=test-project). AI agents run in
headless, non-interactive environments without a TTY or stdin input
handler. Without --quiet, commands that prompt for user confirmation (such
as deleting resources, approving defaults, or selecting unspecified regions)
will pause execution indefinitely waiting for input, causing background task
timeouts. Including --quiet forces non-interactive mode, causing gcloud
to automatically accept safe default choices or fail immediately with an
explicit error if required parameters are missing.
- No Blind Lists: NEVER execute a
list command without --limit,
--filter, or --format.
4. Project and Location Scoping (Critical)
To ensure commands are deterministic, non-interactive, and target the correct
environment, they must explicitly provide project and location scoping.
Explicit Project Target: Do not rely on active configuration defaults.
Always append --project=<PROJECT_ID> to all resource-manipulating and
querying commands (unless running pure local config commands). This avoids
accidental execution against the wrong project.
Prevent Location Prompts: Many Google Cloud resources are regional or
zonal. If the location flag is omitted (e.g., --region, --zone, or
--location), gcloud will trigger an interactive prompt to select a
zone/region. This violates the No Interactivity rule. Always provide
explicit location flags if the command requires them.
Location Discovery: If the correct region, zone, or location for a
service is not known, run discovery commands first (remembering to limit
results if there are many):
Compute Engine (VMs, Networks):
gcloud compute regions list --project=<PROJECT_ID>
gcloud compute zones list --project=<PROJECT_ID>
Other Services (Standard API Style): Many GCP services utilize a
unified locations list command:
gcloud <GROUP> locations list --project=<PROJECT_ID>
- Examples:
gcloud artifacts locations list, gcloud kms locations list, gcloud secrets locations list.
Safety & Guardrails
[!CAUTION] Destructive actions (delete, update, remove) MUST be explicitly
authorized by the user. Never invoke them autonomously unless explicitly
instructed to do so in the context of a safe, pre-approved workflow.
Prohibited Operations (Denylist)
NEVER execute the following commands autonomously. These require explicit
human-in-the-loop authorization:
- Any IAM policy, role, or binding modification (Security): Risk of
privilege escalation, administrative lockout, service disruption, or
unauthorized data exposure.
- No Proactive API Enabling: Assume necessary APIs are enabled. To prevent
unexpected resource provisioning or billing charges, do not proactively try
to enable APIs. User approval is required to enable any API.
- No Proactive
gcloud CLI Installation (Host Modification): Never
autonomously install the Google Cloud CLI (gcloud CLI) or additional
gcloud CLI components (gcloud components install, gcloud components update, or system package manager installs of the gcloud CLI). If the
gcloud binary or a required CLI component is missing, you must inform
the user, ask for explicit user confirmation (e.g., "I am ready to install
the Google Cloud CLI (gcloud). Do you want me to proceed?"), and
strictly stop to wait for the user's positive affirmation before
executing any installation commands.
gcloud * delete (Destructive): Irreversible resource destruction
(e.g., project deletion) or data wiping.
gcloud billing * (Financial): Risk of service disruption or unbounded
costs.
gcloud organizations * (Governance): Org-level changes affect security
posture for all users.
gcloud kms * (Encryption): Risk of permanently locking data.
gcloud infra-manager deployments apply (Destructive): Autonomous IaC
execution can destroy managed resources.
Execution Guidelines
Dry Run (Mandatory): If the --dry-run or --validate-only flag (or
equivalent) is listed in the command help output, ALWAYS include the flag in
the proposed command or initial execution step. ALWAYS preview changes with
--dry-run or --validate-only prior to actual execution.
Long Running Operations: For commands that support it, the --async
flag is highly recommended for long-running operations to avoid blocking the
agentic flow. Note that not every command has an --async flag. For
commands that return an operation ID (whether via --async or by default),
operation status must be polled for completion, if needed for the next step.
Non-Interactive Flag (--quiet): Include --quiet (or -q) on all
proposed or executed commands to guarantee non-interactive execution without
waiting for TTY confirmation prompts.
Structured Workflows
Discovery Workflow
When asked to perform a task on a service that is unfamiliar:
- Invoke Help: Call
gcloud help <COMMAND> on the target leaf command
prior to execution.
- Traverse Command Tree: Run help on command groups (e.g.,
gcloud help compute or gcloud help) to discover available subgroups and commands if
the exact command is unknown.
- Discover Schema: Run
gcloud <GROUP> <RESOURCE> list --limit=1 --format=json to inspect JSON keys before constructing filters or
projections. DO NOT execute unconstrained list commands without scoping
flags (e.g., --limit=1) to prevent context window exhaustion.
- Enforce Data Reduction: Include data reduction flags (
--limit,
--filter, --format) on all command executions.
Quick Reference / Cheat Sheet
| Task |
Command Template |
| Discover Schema |
gcloud <GROUP> <RESOURCE> list --limit=1 --format=json |
| Filtered List |
gcloud <GROUP> <RESOURCE> list --filter="status:RUNNING" |
| Specific Columns |
gcloud <GROUP> <RESOURCE> list --format="json(name, id)" |
| Learn Filters |
gcloud topic filters |
| Learn Formats |
gcloud topic formats |
| Learn Projections |
gcloud topic projections |
| Asynchronous Op |
gcloud <COMMAND> --async |
| Check Operation |
gcloud <GROUP> operations describe <OPERATION_ID> |
| Common commands |
gcloud cheat-sheet |
| List Regions (GCE) |
gcloud compute regions list --project=<PROJECT_ID> |
| List Zones (GCE) |
gcloud compute zones list --project=<PROJECT_ID> |
| List Locations |
gcloud <GROUP> locations list --project=<PROJECT_ID> |
Refer to the
gcloud CLI Scripting Guide
for guidance on using the gcloud CLI in automation.
Reference Directory
CLI Usage: Platform installation, authentication
methods (interactive, headless, ADC, service account keys, impersonation),
and local configuration management.
MCP Usage: Using the Cloud CLI remote MCP
server (run_gcloud_command), project parameter scoping, input files, and
execution guidelines.
Usage Attribution: Standardized usage
attribution tags and multi-skill precedence rules for gcloud CLI, REST
API, and MCP requests.
1---2name: gcloud-23metadata:4 source: https://skillmd.com/skills/google/gcloud-25 version: "1.0.4"6 category: CloudInfrastructureAndServices7description: >-8 Provides safety-critical validation, guardrails, and data reduction for gcloud9 CLI operations across Google Cloud Platform (GCP) services and infrastructure.10 Use when planning, generating, constructing, proposing, describing, or11 executing any gcloud CLI commands - including when answering questions about12 gcloud syntax, or formatting flags. Don't use when writing Google Cloud13 client library code or raw REST/gRPC API requests.14---1516# gcloud CLI Skill for AI Agents1718> [!CAUTION]19>20> ### MANDATORY PRE-CONDITION: EXPLICIT LEAF-LEVEL SYNTAX VALIDATION21>22> All pre-existing knowledge of `gcloud` commands, flags, flag values, and23> positional argument syntax is **stale and prone to hallucination**.24>25> NEVER propose command parameters, output flag options, execute commands, OR26> outline step-by-step plans for any `gcloud` task before validating leaf-level27> syntax via `gcloud help <command>` (or including leaf-level help lookup as a28> mandatory step in the plan).29>30> **Mandatory Action Rules**:31>32> 1. **Direct Execution & Code Generation**: **ALWAYS** invoke `gcloud help33> <leaf_command>` (e.g. `gcloud help compute instances create` or `gcloud34> help sql instances create`) before proposing or executing the final35> command syntax, **UNLESS** the user prompt already provides `gcloud help`36> output, states to assume command syntax is already validated, or instructs37> not to execute any commands. When instructed not to execute any commands,38> **NEVER** invoke `run_command` (not even for `gcloud help` or directory39> listing commands like `ls`); read bundled reference files40> (`references/cli-usage.md`, `references/mcp-usage.md`, and41> `references/attribution.md`) directly with `read_file`.42>43> 2. **Planning & Strategy Queries**: When asked for a plan, strategy, or next44> steps to achieve a user goal (e.g., *"What is your plan to accomplish45> X..."*), the response **MUST explicitly include running `gcloud help46> <leaf_command>`** as Step 1 of the plan before proposing flags or47> executing commands.48>49> 3. **Non-Transitive Validation**: Parent command group help (e.g. `gcloud50> help compute`) is not sufficient for leaf-level syntax validation.51> Validation must occur at the specific leaf subcommand level.52>53> 4. **FORBIDDEN Web Search Fallback**: NEVER use `search_web`, web search, or54> external documentation search tools for gcloud CLI syntax. `gcloud help55> <leaf_command>` is the **EXCLUSIVE** authorized authority for command56> syntax.57>58> 5. **User Flag & Project Preservation**: When proposing intermediate command59> steps, **ALWAYS** preserve all user-specified flags (including60> `--project=<project_id>`) in the proposed response text.61>62> 6. **Mandatory Plan Template**: When generating a plan, the response **MUST**63> copy this exact 4-step structure:64>65> - **Step 1**: Syntax Validation via `gcloud help <leaf_command>`66> - **Step 2**: Parameter Verification (confirming required and optional67> flags, and explicitly checking if the `--dry-run` or `--validate-only`68> flag is supported)69> - **Step 3**: Dry-Run Command Proposal (If `--dry-run` or70> `--validate-only` is supported, there MUST be a `--dry-run` or71> `--validate-only` invocation before the next step.)72> - **Step 4**: Command Proposal & Authorization (If the command is on the73> "Prohibited Operations" denylist, state that autonomous execution is74> forbidden, and the user MUST be explicitly asked for authorization to75> proceed. If the command is NOT on the denylist, propose or proceed76> with execution, while following *ALL* "Execution Constraints" below.)7778This document provides essential guidelines and best practices for AI agents79interacting with the Google Cloud SDK (`gcloud` CLI). Following these rules is80critical to avoid hallucinated commands, flags, flag values, and positional81argument syntax, prevent destructive actions, and minimize context window usage.8283## Usage Attribution8485**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you86MUST read and follow the instructions in87[Usage Attribution](references/attribution.md). If a more specific product or88domain skill (e.g., `cloud-run-basics`, `bigquery-basics`, `gke-basics`) is89also loaded or active for the current task, **ALWAYS** use that specific90skill's `skill:<name>` attribution tag instead of `skill:gcloud`. For commands91executed directly in the terminal when no product-specific skill applies (never92in generated scripts, Terraform, or user code), prefix `gcloud` with93`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:gcloud)"`94and append `agent-skills/1.0 (skill:gcloud)` to `User-Agent` headers.9596## Execution Modes9798AI agents can interact with Google Cloud resources in two primary ways:99100- **Direct CLI Execution**: Executing `gcloud` commands directly in a local or101 automated shell environment. See [CLI Usage](references/cli-usage.md) for102 installation, authentication flows, and configuration management.103- **Model Context Protocol (MCP)**: Invoking structured tools via the Cloud104 CLI remote MCP server (`run_gcloud_command`). See105 [MCP Usage](references/mcp-usage.md) for tool schemas, parameter rules, and106 server configuration.107108## Core Principles109110### 1. Explicit Command Validation (Mandatory)111112* **Action**: **ALWAYS** call `gcloud help <command>` for the *exact* command113 that is intended to be run (e.g., `gcloud help compute instances create`).114* **Verify**: Ensure the command, flags, flag values, and positional argument115 syntax are valid for that specific leaf command before attempting execution116 or presenting plans. Validation is not transitive from parent groups.117118### 2. Data Reduction Strategies (Mandatory)119120Minimize the volume of data returned by `gcloud` to save context window space121and reduce latency. DO NOT execute any `list` command without including at least122one data reduction flag (`--limit`, `--filter`, or `--format`).123124* **Projection**: Use `--format="json(key1, key2, ...)"` to select only the125 specific fields needed for the task. To understand the advanced projection126 and formatting syntax, refer to `gcloud topic projections` and `gcloud topic127 formats`.128129* **Limiting**: Use `--limit=N` to cap the number of resources returned.130131* **Filtering**: Use `--filter` to narrow down results server-side. Prioritize132 `:` for pattern matching and never quote the right side of the colon. Treat133 the entire filter flag as a singular string without quoting or escaping134 characters. To study the filter expression syntax, refer to `gcloud topic135 filters`.136137* **Schema Discovery**: Unconstrained resource lists can quickly exhaust the138 context window with redundant data. To prevent this, discover a resource's139 schema before executing queries. If unsure of the JSON key path for140 projecting fields (`--format`) or filtering (`--filter`), run the targeted141 resource's list command (if supported) with a single-item limit:142143 ```bash144 gcloud <GROUP> <RESOURCE> list --limit=1 --format=json145 ```146147 Examine this single instance's JSON structure to safely identify the correct148 schema keys before requesting full or filtered datasets.149150### 3. Execution Constraints151152* **Single Commands**: Execute a single `gcloud` command at a time. No command153 chaining or sequencing.154* **No Shell Operators**: Do not use command substitution (`$(...)`), pipes155 (`|`), or redirection (`>`, `>>`, `<`). This is to increase command safety156 and ensure commands are more easily understandable and reviewable by users.157* **Non-Interactive Execution (`--quiet` / `-q`)**: Pass the `--quiet` (or158 `-q`) global flag on all execution commands (e.g., `gcloud pubsub topics159 delete temp-topic --quiet --project=test-project`). AI agents run in160 headless, non-interactive environments without a TTY or `stdin` input161 handler. Without `--quiet`, commands that prompt for user confirmation (such162 as deleting resources, approving defaults, or selecting unspecified regions)163 will pause execution indefinitely waiting for input, causing background task164 timeouts. Including `--quiet` forces non-interactive mode, causing `gcloud`165 to automatically accept safe default choices or fail immediately with an166 explicit error if required parameters are missing.167* **No Blind Lists**: NEVER execute a `list` command without `--limit`,168 `--filter`, or `--format`.169170### 4. Project and Location Scoping (Critical)171172To ensure commands are deterministic, non-interactive, and target the correct173environment, they must explicitly provide project and location scoping.174175* **Explicit Project Target**: Do not rely on active configuration defaults.176 Always append `--project=<PROJECT_ID>` to all resource-manipulating and177 querying commands (unless running pure local config commands). This avoids178 accidental execution against the wrong project.179180* **Prevent Location Prompts**: Many Google Cloud resources are regional or181 zonal. If the location flag is omitted (e.g., `--region`, `--zone`, or182 `--location`), `gcloud` will trigger an interactive prompt to select a183 zone/region. This violates the **No Interactivity** rule. Always provide184 explicit location flags if the command requires them.185186* **Location Discovery**: If the correct region, zone, or location for a187 service is not known, run discovery commands first (remembering to limit188 results if there are many):189190 * **Compute Engine (VMs, Networks)**:191192 * `gcloud compute regions list --project=<PROJECT_ID>`193 * `gcloud compute zones list --project=<PROJECT_ID>`194195 * **Other Services (Standard API Style)**: Many GCP services utilize a196 unified `locations list` command:197198 * `gcloud <GROUP> locations list --project=<PROJECT_ID>`199 * *Examples*: `gcloud artifacts locations list`, `gcloud kms locations200 list`, `gcloud secrets locations list`.201202## Safety & Guardrails203204> [!CAUTION] **Destructive actions (delete, update, remove) MUST be explicitly205> authorized by the user.** Never invoke them autonomously unless explicitly206> instructed to do so in the context of a safe, pre-approved workflow.207208### Prohibited Operations (Denylist)209210NEVER execute the following commands autonomously. These require explicit211human-in-the-loop authorization:212213* **Any IAM policy, role, or binding modification** (Security): Risk of214 privilege escalation, administrative lockout, service disruption, or215 unauthorized data exposure.216* **No Proactive API Enabling**: Assume necessary APIs are enabled. To prevent217 unexpected resource provisioning or billing charges, do not proactively try218 to enable APIs. User approval is required to enable any API.219* **No Proactive `gcloud` CLI Installation** (Host Modification): Never220 autonomously install the Google Cloud CLI (`gcloud` CLI) or additional221 `gcloud` CLI components (`gcloud components install`, `gcloud components222 update`, or system package manager installs of the `gcloud` CLI). If the223 `gcloud` binary or a required CLI component is missing, you **must** inform224 the user, ask for explicit user confirmation (e.g., *"I am ready to install225 the Google Cloud CLI (`gcloud`). Do you want me to proceed?"*), and226 **strictly stop** to wait for the user's positive affirmation before227 executing any installation commands.228* **`gcloud * delete`** (Destructive): Irreversible resource destruction229 (e.g., project deletion) or data wiping.230* **`gcloud billing *`** (Financial): Risk of service disruption or unbounded231 costs.232* **`gcloud organizations *`** (Governance): Org-level changes affect security233 posture for all users.234* **`gcloud kms *`** (Encryption): Risk of permanently locking data.235* **`gcloud infra-manager deployments apply`** (Destructive): Autonomous IaC236 execution can destroy managed resources.237238### Execution Guidelines239240* **Dry Run (Mandatory)**: If the `--dry-run` or `--validate-only` flag (or241 equivalent) is listed in the command help output, ALWAYS include the flag in242 the proposed command or initial execution step. ALWAYS preview changes with243 `--dry-run` or `--validate-only` prior to actual execution.244245* **Long Running Operations**: For commands that support it, the `--async`246 flag is highly recommended for long-running operations to avoid blocking the247 agentic flow. Note that not every command has an `--async` flag. For248 commands that return an operation ID (whether via `--async` or by default),249 operation status must be polled for completion, if needed for the next step.250251* **Non-Interactive Flag (`--quiet`)**: Include `--quiet` (or `-q`) on all252 proposed or executed commands to guarantee non-interactive execution without253 waiting for TTY confirmation prompts.254255## Structured Workflows256257### Discovery Workflow258259When asked to perform a task on a service that is unfamiliar:2602611. **Invoke Help**: Call `gcloud help <COMMAND>` on the target leaf command262 prior to execution.2632. **Traverse Command Tree**: Run help on command groups (e.g., `gcloud help264 compute` or `gcloud help`) to discover available subgroups and commands if265 the exact command is unknown.2663. **Discover Schema**: Run `gcloud <GROUP> <RESOURCE> list --limit=1267 --format=json` to inspect JSON keys before constructing filters or268 projections. DO NOT execute unconstrained `list` commands without scoping269 flags (e.g., `--limit=1`) to prevent context window exhaustion.2704. **Enforce Data Reduction**: Include data reduction flags (`--limit`,271 `--filter`, `--format`) on all command executions.272273## Quick Reference / Cheat Sheet274275Task | Command Template276------------------ | ----------------------------------------------------------277Discover Schema | `gcloud <GROUP> <RESOURCE> list --limit=1 --format=json`278Filtered List | `gcloud <GROUP> <RESOURCE> list --filter="status:RUNNING"`279Specific Columns | `gcloud <GROUP> <RESOURCE> list --format="json(name, id)"`280Learn Filters | `gcloud topic filters`281Learn Formats | `gcloud topic formats`282Learn Projections | `gcloud topic projections`283Asynchronous Op | `gcloud <COMMAND> --async`284Check Operation | `gcloud <GROUP> operations describe <OPERATION_ID>`285Common commands | `gcloud cheat-sheet`286List Regions (GCE) | `gcloud compute regions list --project=<PROJECT_ID>`287List Zones (GCE) | `gcloud compute zones list --project=<PROJECT_ID>`288List Locations | `gcloud <GROUP> locations list --project=<PROJECT_ID>`289290Refer to the291[gcloud CLI Scripting Guide](https://docs.cloud.google.com/sdk/docs/scripting-gcloud.md.txt)292for guidance on using the gcloud CLI in automation.293294## Reference Directory295296- [CLI Usage](references/cli-usage.md): Platform installation, authentication297 methods (interactive, headless, ADC, service account keys, impersonation),298 and local configuration management.299300- [MCP Usage](references/mcp-usage.md): Using the Cloud CLI remote MCP301 server (`run_gcloud_command`), project parameter scoping, input files, and302 execution guidelines.303304- [Usage Attribution](references/attribution.md): Standardized usage305 attribution tags and multi-skill precedence rules for `gcloud` CLI, REST306 API, and MCP requests.