with one click
gcp-setup
// 🐉 Initial Google Cloud environment verification and authentication setup. Use when starting a new session to ensure correct identities across gcloud, ADC, and kubectl.
// 🐉 Initial Google Cloud environment verification and authentication setup. Use when starting a new session to ensure correct identities across gcloud, ADC, and kubectl.
🐉 [SRE] Use when the user wants to set up Google Managed MCP (OneMCP) servers for their Gemini CLI environment. Automates enabling services, MCP servers, generating API keys, and configuring ~/.gemini/settings.json.
🐉 Detects anomalies in time-series data from various sources.
🐉 Skill for interacting with and analyzing Google Cloud Logging and Error Reporting. Use this when you need to process large JSON logs from GCP or convert them to Apache format for easier analysis.
🐉 Fetches and parses time-series data from various sources.
🐉 [SRE] Use when you need to follow established SRE playbooks for GCP/GKE investigations, including infrastructure discovery and common mitigation steps.
🐉 [SRE] Manage Service Level Objectives (SLOs) on Google Cloud. Use when you need to discover Monitoring Services, list existing SLOs, or create new SLOs (Availability/Latency) via the REST API when gcloud commands are unavailable.
| name | gcp-setup |
| description | 🐉 Initial Google Cloud environment verification and authentication setup. Use when starting a new session to ensure correct identities across gcloud, ADC, and kubectl. |
| metadata | {"author":"Google","version":"0.0.2"} |
Use this skill to verify and harmonize your GCP identities at the start of an investigation or session.
gcp-whoami.sh script to check all three major identities (gcloud, ADC, and kubectl).gcloud: gcloud auth login [ACCOUNT]gcloud auth application-default logingcloud container clusters get-credentials [CLUSTER] --region [REGION] --project [PROJECT]scripts/gcp-whoami.sh: Displays current identities for gcloud, ADC, and kubectl.If SAFE_MODE="enabled" is found in the environment or .env file, you MUST activate the safe-sre-investigator skill immediately after verifying the initial setup. This ensures all subsequent operations use read-only/non-mutating service accounts.
Note that the SAFE_MODE might impact kubectl authorization via RBAC.