gcloud-cli-health-check
This skill may run in an automated/scheduled context with no user present. Execute all steps autonomously without asking clarifying questions. For write actions (send, post, create, update, delete), only take them if explicitly requested. When in doubt, produce a report of what you found.
Critical: Use Desktop Commander — Not the Bash Tool
All gcloud commands MUST run via mcp__Desktop_Commander__start_process. The Bash tool runs in a sandboxed Linux environment where gcloud is not installed AND the sandbox proxy returns 403 blocked-by-allowlist for every Google endpoint (dl.google.com, sdk.cloud.google.com, oauth2.googleapis.com, www.googleapis.com, accounts.google.com). The user's Mac has Google Cloud SDK installed at /opt/homebrew/bin/gcloud with auth already configured.
✅ mcp__Desktop_Commander__start_process → runs on user's Mac → gcloud found, auth available
❌ Bash tool → runs in Linux sandbox → gcloud not found, Google blocked
If Desktop Commander is unavailable, do NOT try to install gcloud in the sandbox — it is impossible (no network access to Google, no sudo). Write a report documenting the block and stop.