gcp-debug

Diagnose customer GCP issues with read-only inspections of resources and logs.

Updated Aug 23, 2026

Search Tags:#debugging #logs #gcp #google cloud #iam #read-only #cloud-run

Ready to run

npx skills add https://github.com/meganide/claude --skill gcp-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gcp-debug
Source: https://github.com/meganide/claude/tree/main/skills/gcp-debug
Command: npx skills add https://github.com/meganide/claude --skill gcp-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug customer GCP instances with read-only operations - view logs, check settings, inspect Cloud Run services, and diagnose issues. Use when investigating customer infrastructure problems.

Core Features & Use Cases

Read-only diagnostics: query and inspect GCP resources without making changes.
Observability checks: view logs, monitor Cloud Run configurations, IAM policies, and service statuses.
Use Case: When a customer's infrastructure problem is suspected, quickly assess state and identify misconfigurations without altering resources.

Quick Start

Use the gcp-debug skill to start by listing projects, describing services, and fetching logs from the target customer project.

Frequently Asked Questions about gcp-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug customer GCP infrastructure without making changes to resources?▼

To diagnose Cloud Run issues read-only, fetch service logs and describe service configurations to assess the current state. This approach verifies IAM policies, monitors Cloud Run settings, and identifies misconfigurations using non-destructive gcloud commands without altering resources.

Can I inspect IAM policies and Cloud SQL configurations safely during a GCP investigation?▼

Yes, you can inspect IAM policies and Cloud SQL configurations safely during a GCP investigation. The process enforces a strict read-only workflow that queries settings and service statuses without executing any create, update, delete, or patch actions on the infrastructure.

What is the best way to quickly assess a customer's Google Cloud state when a problem is suspected?▼

The best way to assess a customer's Google Cloud state is to start by listing projects, describing services, and fetching logs. This read-only diagnostic approach quickly identifies misconfigurations and checks service statuses across GCP without risking destructive changes.

What are the limitations of using read-only gcloud commands for GCP diagnostics?▼

The limitation of read-only gcloud commands for GCP diagnostics is that they cannot fix the issues they uncover. Because the workflow strictly prohibits create, update, delete, or patch actions, it can only identify misconfigurations and verify resource states without applying corrective measures.