ALWAYS check before using gcloud commands. Guide for GCP-related skills and tools.
You have specialized GCP debugging skills. Use these instead of raw gcloud commands for consistent, well-documented workflows.
Simple, single gcloud command query?
ā Use gcp-logs skill
gcloud logging read commandsComplex investigation requiring multiple steps? ā Use Task tool with GCP agents (conserves context)
gcp-locator - Fetch logs from multiple services, save to /tmpgcp-analyzer - Filter logs, diagnose service issues, check IAMgcp-pattern-finder - Correlate logs across services, build timelinesJust need to fetch logs broadly?
ā Use gcp-locator agent only
Investigating single service issue?
ā Use gcp-locator + gcp-analyzer agents
Need to correlate across services or find patterns?
ā Use all three: gcp-locator + gcp-analyzer + gcp-pattern-finder
Need to understand GCP IAP authentication? ā Check documentation or use WebFetch
gcloud auth print-identity-token| Type | Name | Purpose |
|---|---|---|
| Skill | gcp-logs | Simple log queries (single gcloud command) |
| Agent | gcp-locator | Fetch logs from multiple services/ranges |
| Agent | gcp-analyzer | Analyze service logs, diagnose issues |
| Agent | gcp-pattern-finder | Correlate logs, find patterns, build timelines |
Only use gcloud directly when:
For systematic GCP work, use the specialized skills above.
gcloud - Primary CLI toolgcloud logging read - Cloud Logging queries (use gcp-logs skill)gcloud auth print-identity-token - Get IAP tokens for service accessCheck authentication before any GCP operation:
gcloud auth list
gcloud config get-value project