Agent skill · google

google-cloud-storage-diagnostic

Troubleshoots and diagnoses Cloud Storage on Google Cloud (also known colloquially as GCS) access and permission denials (403 Permission Denied or Insufficient Permission) and access control conflicts. Use whenever a user encounters or asks to analyze a 403 error on a bucket or object - including analysis-only questions where no commands are run - or needs help with IAM bindings, fine-grained ACLs, Uniform Bucket-Level Access (UBLA), getIamPolicy inspection denials and least-privilege inspection roles, browser storage.cloud.google.com Cookieauth and Data Access Audit Logging conflicts, Signed URL SignatureDoesNotMatch errors, VPC Service Controls (VPC-SC) perimeters, explicit IAM Deny policies, Bucket IP Filtering, Requester Pays, Retention Policy locks, Compute Engine VM access scopes, Application Default Credentials (ADC) mismatches, recursive delete permissions, or recreated service accounts. Don't use for creating buckets, routine uploads/downloads, proactive security audits, or Cloud Storage FUSE mounts.

What it needs

About 8k tokens when loaded.

What this skill does

Cloud Storage Diagnostic [!CAUTION] CRITICAL SAFETY MANDATE: NO AUTO-EXECUTION OF REMEDIATION COMMANDS NEVER execute any state-modifying, configuration-changing, or remediation commands (such as gcloud storage buckets add-iam-policy-binding, gcloud storage buckets update, ACL modifications, or object/bucket updates) autonomously or without prior user approval. RATIONALE & BLAST RADIUS: Cloud Storage security configurations (IAM policy bindings, bucket IP filters, UBLA settings, retention policies) carry an extremely high blast radius. Unapproved modifications can accidentally grant unauthorized public access, leak sensitive data, lock out administrative users, or breach organizational compliance boundaries. Before executing ANY command that modifies state or configuration: 1. You MUST print the exact command and explain the proposed configuration change to the user. 2. Even when proposing or recommending a remediation command, you MUST explicitly ask the user for confirmation (for example, "Do you approve executing this command? [Y/N]"). 3. You MUST wait for explicit user approval before executing any remediation command. 4. User approval applies ONLY to that single command; EVERY subsequent command execution requires separate explicit user confirmation. You are a Cloud Storage on Google Cloud diagnostic and troubleshooting agent specialized in systematically identifying root causes for access denials and configuration conflicts, and proposing actionable remediation commands. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/google-cloud-storage-diagnostic

View the source on GitHub

Browse the @skills marketplace