Agent skill · google
google-cloud-filestore-log-troubleshooting
Diagnoses and resolves Filestore client mount failures on Google Cloud, permission errors (EACCES), and network timeouts (ETIMEDOUT). Use when an NFS mount hangs or fails from a Compute Engine VM, GKE pod, Cloud Run service, or Vertex AI workload, when `mount.nfs` reports "Connection timed out" or "access denied by server", when checking whether VPC ingress firewall rules or `nfsExportOptions` allow a client IP, or when a previously working Filestore share suddenly stops mounting after an administrative change. Don't use for Cloud Storage (GCS) buckets, Persistent Disk, or Cloud NetApp Volumes, and don't use for Filestore capacity scaling or backup and export-policy auditing.
What it needs
About 6k tokens when loaded.
What this skill does
<!-- disableFinding(LINEOVER80) --> Filestore Log-Based Troubleshooting Diagnoses, troubleshoots, and remediates Filestore client mount failures, permission errors (EACCES), and network timeouts (ETIMEDOUT) across projects. Prerequisites & Quick Start Required IAM roles on target project(s) (and Shared VPC host project if applicable): Read: roles/file.viewer (instance & export ACLs), roles/compute.networkViewer (VPC firewall rules), roles/logging.viewer (Cloud Audit & GKE CSI logs), roles/mcp.toolUser (if using MCP tools). Write (Remediation only): roles/file.editor (export ACL updates), roles/compute.securityAdmin (firewall rule creation). Authenticate, verify billing/APIs, and configure your environment: Attribution Prefix every gcloud command provided or executed with the skill metrics environment: On direct REST API calls, append HTTP header: User-Agent: gcs-skills/1.0 (skill:google-cloud-filestore-log-troubleshooting). Conceptual & Informational Queries (CRITICAL) For purely conceptual, architectural, or educational questions (e.g., "What causes EACCES on Filestore?", "Why does GKE Node IP appear instead of Pod IP?", "What ports does Filestore require?", "Explain root squash"): Rule: Answer immediately using pre-trained knowledge and the workflow rules below. Answering directly minimizes tool latency and token usage when the user only seeks architectural guidance. Constraint: Do not execute external tool calls or API requests for basic knowledge questions. Handling "No-Command" Constraints (CRITICAL) If the user prompt contains constraints like "Do not execute commands", "without executing", or "read-only": Rule: Strictly avoid calling runcommand to execute any shell, Python, or gcloud commands. Discovery: 1. First, check if Filestore MCP tools (getinstance, listinstances) are available and use them (API calls, not command executions). 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-filestore-log-troubleshooting