What problem does it solve? Google Cloud's CLI defaults are frequently wrong for production (zonal Cloud SQL, us multi-region buckets, flat concurrency assumptions), IAM changes propagate unpredictably, and cost or incident investigations fail silently when flags like --freshness are missed. This Skill encodes verified defaults, safe deployment workflows, and audit procedures so agents operate Google Cloud correctly the first time. ## Core Features & Use Cases - Verified CLI discipline: 25 core rules checked against Google Cloud SDK 584.0.0, covering gcloud help validation, --quiet in headless runs, explicit --project scoping, and human-approval gates for IAM, delete, billing, and KMS operations. - Safe Cloud Run shipping: deploy with --no-traffic --tag, verify on the tag URL, shift 10% traffic, and roll back by revision, with correct handling of concurrency (80 x vCPU vs flat 80), timeout limits, and revision-immutable scaling flags. - IAM and storage audits: flag default service accounts with roles/editor, user-managed keys, missing deny policies, soft-delete billing, and lifecycle rules that raise costs instead of lowering them. - Use Case: Given a Cloud Run service YAML that saturates early and kills requests at five minutes, identify the 300s timeout default, the concurrency miscalculation, and ship the fix to 10% of traffic before full promotion. ## Quick Start Ask the agent to audit your Google Cloud project's IAM policy or review a Cloud Run service configuration for production readiness.