gcloud

Google Cloud SDK command-line tools. Use for GCP automation.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

gcloud is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Google Cloud SDK command-line tools. Use for GCP automation.

Teams using gcloud should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/gcloud/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/gcloud/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/gcloud/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How gcloud Compares

Feature / Agent	gcloud	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Google Cloud SDK command-line tools. Use for GCP automation.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Google Cloud CLI (`gcloud`)

The `gcloud` CLI is part of the Google Cloud SDK. It manages authentication, local configuration, and developer workflows for GCP.

## When to Use

- **App Engine / Cloud Run**: `gcloud app deploy` and `gcloud run deploy` are the standard ways to ship code.
- **Kubernetes**: `gcloud container clusters get-credentials` is essential for GKE access.
- **Auth**: `gcloud auth login` sets up Application Default Credentials (ADC).

## Quick Start

```bash
# Initialize
gcloud init

# Authenticate for local code (ADC)
gcloud auth application-default login

# Deploy to Cloud Run
gcloud run deploy my-service --source .
```

## Core Concepts

### Components

Installable modules. `kubectl`, `beta`, `gke-gcloud-auth-plugin`.
`gcloud components install kubectl`

### Configurations

Use named configurations to switch between accounts/projects.
`gcloud config configurations create dev`

### Alpha / Beta

GCP releases features rapidly. Many commands live under `gcloud beta`.

## Best Practices (2025)

**Do**:

- **Use ADC**: For local development, `application-default login` is the correct way to auth your local Python/Node scripts.
- **Use `gcloud config set project`**: Don't pass `--project` to every command. Set the context.
- **Scripting**: Use `--format="json"` and `jq` for reliable automation.

**Don't**:

- **Don't use Service Account Keys locally**: They are risky. Use User Credentials (ADC) for local dev.

## References

- [gcloud CLI Documentation](https://cloud.google.com/sdk/gcloud)