Skip to content
Skills Library
DevOps & cloud · Tool integration

gcloud

/gcloud

Use the gcloud CLI from a Centaur sandbox, where iron-proxy injects Google Cloud credentials on the wire. Use before any gcloud command, Google Cloud deploy, Cloud Run, Cloud Build, Artifact Registry, Cloud Storage, or IAM task, and whenever gcloud reports no credentialed account, asks you to run `gcloud auth login`, or a Google API returns 401, 403, or SERVICE_DISABLED.

Repository
centaur ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use the gcloud CLI from a Centaur sandbox, where iron-proxy injects Google Cloud credentials on the wire. Use before any gcloud command, Google Cloud deploy, Cloud Run, Cloud Build, Artifact Registry, Cloud Storage, or IAM task, and whenever gcloud reports no credentialed account, asks you to run `gcloud auth login`, or a Google API returns 401, 403, or SERVICE_DISABLED.

Original author description

Use the gcloud CLI from a Centaur sandbox, where iron-proxy injects Google Cloud credentials on the wire. Use before any gcloud command, Google Cloud deploy, Cloud Run, Cloud Build, Artifact Registry, Cloud Storage, or IAM task, and whenever gcloud reports no credentialed account, asks you to run `gcloud auth login`, or a Google API returns 401, 403, or SERVICE_DISABLED.

How it works

  1. Setup
  2. Rules
  3. Known limits
  4. Failures
Original SKILL.md headings · 45 lines, 663 words
SKILL.md preview
---
name: gcloud
description: "Use the gcloud CLI from a Centaur sandbox, where iron-proxy injects Google Cloud credentials on the wire. Use before any gcloud command, Google Cloud deploy, Cloud Run, Cloud Build, Artifact Registry, Cloud Storage, or IAM task, and whenever gcloud reports no credentialed account, asks you to run `gcloud auth login`, or a Google API returns 401, 403, or SERVICE_DISABLED."
---

# gcloud in a Centaur sandbox

The sandbox has no local Google login. When the current principal holds a GCP credential grant, iron-proxy adds a real `Authorization` header to each Google API request as it leaves the sandbox. So `gcloud auth list` shows no credentialed account even when access works. **Never report "no GCP credentials" or "no authenticated account" because of `gcloud auth list` or `gcloud config get-value account`.** Make a real call first.

## Setup

gcloud refuses to send requests without a local credential. Give it a placeholder token, which the proxy replaces:

```bash
printf 'placeholder' > /tmp/gcp-placeholder-token
export CLOUDSDK_AUTH_ACCESS_TOKEN_FILE=/tmp/gcp-placeholder-token
gcloud run services list --project=<project> --region=<region>
```

Set the variable in the same shell command as the gcloud call, because shell state does not persist between tool calls. `--access-token-file=/tmp/gcp-placeholder-token` on a single command works too. With the variable set, `gcloud auth print-access-token` prints `placeholder`. Scripts that pass that value in an `Authorization` header still work, because the proxy overwrites the header.

## Rules

- Always pass `--project`. There is no default project.
- If a call fails with `SERVICE_DISABLED` for an API in a project you did not name (often Cloud Resource Manager), gcloud billed the request to the wrong quota project. Retry with `--billing-project=<a project where that API is enabled>`.
- Before acting, find out which identity you have. It depends on the surface:
  - DMs usually use the requester's personal Google OAuth.
  - Shared channels use service accounts granted to the channel.
  - A principal can hold several GCP credentials, scoped to different Google API hosts, so Cloud Run and Cloud Storage may act as different accounts.
- To see the principal for a host, make a harmless read that is likely to be denied. Storage errors name the caller: `gcloud storage ls gs://<bucket-you-cannot-read>` → `<principal> does not have storage.objects.list access`.
- Personal credentials act as a real person. Stay within the project the user named, read before you write, and ask before any destructive or IAM-changing command unless the user already asked for that exact change.
- Never print, log, or store real tokens. You never hold one anyway, so do not try to extract one.

## Known limits

- **ID tokens cannot be minted.** `gcloud auth print-identity-token` fails with `No identity token can be obtained from the current credentials`. Calls to private Cloud Run services work only for hosts where the deployment configured an ID-token credential. Anything else, including smoke tests that call `print-identity-token`, has to be run by a human from an authenticated shell. Give them the exact command.
- **Scripts that read `gcloud config get-value account` get an empty value.** Read the script before running it, and pass the account explicitly or hand that step to a human.
- **`bq` fails TLS verification through the proxy.** Use `gcloud` or a Google client library instead.
- **Client libraries** start from the sandbox's mock `GOOGLE_APPLICATION_CREDENTIALS`. They work when the proxy handles the token exchange for that credential. If you see `invalid_grant: account not found` or signing errors for `mock@creds.com`, switch to gcloud. Signed URLs and `signBlob` never work.

## Failures

| Symptom | Meaning | Action |
|---|---|---|
| `You do not currently have an active account selected` | No placeholder token was set. | Set `CLOUDSDK_AUTH_ACCESS_TOKEN_FILE` and retry. |
| `401 ACCESS_TOKEN_TYPE_UNSUPPORTED`, `Invalid Credentials` | The proxy did not inject a usable token for that host, usually because the principal has no GCP grant covering it. | Report the missing grant. Follow the `auth-failure-log-triage` skill for proxy evidence. |
| `403 PERMISSION_DENIED` naming a permission | The injected identity lacks IAM for that action. | Report the principal, the permission, and the resource. Offer the `gcloud ... add-iam-policy-binding` command for an owner to run. Do not retry with another identity. |
| `SERVICE_DISABLED` for the target project | The API is off in that project. | Ask an owner to run `gcloud services enable <api> --project=<project>`, unless you were asked to enable it and have `serviceusage.services.enable`. |

Versions

RepositoryScoreLicence
This page · paradigmxyz/centaur100MIT
google/skills100Apache-2.0
google/skills100Apache-2.0
TerminalSkills/skills100Apache-2.0
dreamlab-ai/agentbox100AGPL-3.0
rittmananalytics/wire-plugin100Apache-2.0
yangshun2005/skills-cn100Apache-2.0
hamzabellouch/agent-skills100MIT
AkshatNaruka/aidentity100MIT

Database snapshot: 13.11.2026 · package version cbea8a4791bf (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100gcloud-cli-health-check
    Run a Google Cloud CLI (gcloud) health check — verify installation, authentication, active project, recommended region, enabled APIs (run, cloudbuild, artifactregistry, secretmanager, cloudresourcemanager, iam, plus gmail/calendar/monitoring/logging), API access token, billing,…
  • 85gcloud-auth-verification
    Guidelines for identifying and resolving missing Google Cloud authentication and Application Default Credentials (ADC). Use this skill if `gcloud`, `bq`, `dataform`, or Python libraries return authentication errors.
  • 100gcp
    Manages Google Cloud architecture, IAM, gcloud, Cloud Run, GKE clusters and managed services. Use when writing or reviewing gcloud commands, auditing project IAM or service accounts, setting up Workload Identity Federation, deploying or debugging Cloud Run, creating a GKE…
  • 100gcloud-setup
    Install and authenticate the Google Cloud CLI (gcloud, gsutil, bq) on macOS. Use when the user needs to set up gcloud from scratch, re-authenticate, add OAuth scopes for a specific Google API (Search Console, Drive, Sheets, etc.), or fix Application Default Credentials (ADC) issues.
  • 100gcloud-usage
    This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
  • 100cloud-run
    Deploy and manage containerized workloads on Cloud Run. Covers service creation, traffic splitting, IAM, VPC connectivity, secrets integration, auto-scaling, and gcloud CLI patterns. Warns before billable deployments. Use when the user mentions: deploy to cloud run, create cloud…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.