What problem does it solve? Choosing the correct Google Cloud authentication method is confusing: developers often misuse service account keys, mix up gcloud CLI auth with Application Default Credentials, or fail to secure production workloads. This Skill provides structured guidance to pick the right identity and credential approach for any scenario. ## Core Features & Use Cases - Human Authentication Guidance: Covers gcloud CLI login, Application Default Credentials for local development, service account impersonation, Workforce Identity Federation, IAP, and Identity Platform. - Service-to-Service Authentication: Explains attaching service accounts to Compute Engine and Cloud Run, Workload Identity Federation for GKE and external clouds, OIDC ID tokens, and short-lived credentials. - Authorization Best Practices: Details IAM allow policies, predefined versus custom roles, API key restrictions, and OAuth 2.0 access scopes. - Use Case: A developer deploying a Cloud Run service that calls Cloud SQL learns to attach a custom least-privilege service account and grant roles/cloudsql.client instead of downloading a service account key. ## Quick Start Ask how to authenticate a Python script running locally to access a Google Cloud Storage bucket.