google-cloud

Inspect GCP resources using the local gcloud and bq CLIs directly. Auth is handled entirely by the gcloud CLI - no OAuth client setup, no wrapper scripts.

Important

• Every operation is a plain gcloud or bq invocation. There is no helper script in this skill.
• Default posture is read-only for BigQuery. Dry-run before executing any query.
• Never run destructive BQ operations: bq rm, bq load, bq update, bq cp, bq set-iam-policy, or any bq mk that creates production resources.
• Auth tokens must never appear in chat.
• Never skip the context.json update. Any time you discover a new account/project/dataset/service mapping in a task, write it to ~/.gcloud/google-cloud-skill/context.json before ending your turn - see "Context file" below. This is a required step, not an optional convenience, even in a task that is otherwise finished.

Authentication