Skip to content
Skill

Google cloud filestore log troubleshooting

Diagnoses and resolves Filestore client mount failures on Google Cloud, permission errors (EACCES), and network timeouts (ETIMEDOUT)

Install
Scripts
Python
Platforms
Claude Code, Codex, Cursor
GitHub stars
24.4K
Last commit
today
License
Apache-2.0
Listing updated
today

When your agent uses it

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.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 8 files (71 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/google-cloud-filestore-log-troubleshooting to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/google-cloud-filestore-log-troubleshooting &&
cp -R "$tmp/skills/cloud/google-cloud-filestore-log-troubleshooting" ~/.claude/skills/google-cloud-filestore-log-troubleshooting &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/google-cloud-filestore-log-troubleshooting inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/google-cloud-filestore-log-troubleshooting to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/google-cloud-filestore-log-troubleshooting &&
cp -R "$tmp/skills/cloud/google-cloud-filestore-log-troubleshooting" ~/.agents/skills/google-cloud-filestore-log-troubleshooting &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/google-cloud-filestore-log-troubleshooting inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/google-cloud-filestore-log-troubleshooting to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/google-cloud-filestore-log-troubleshooting &&
cp -R "$tmp/skills/cloud/google-cloud-filestore-log-troubleshooting" ~/.cursor/skills/google-cloud-filestore-log-troubleshooting &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/google-cloud-filestore-log-troubleshooting inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/google/skills.git --path skills/cloud/google-cloud-filestore-log-troubleshooting

Or copy the folder to ~/.gemini/skills/google-cloud-filestore-log-troubleshooting yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/google-cloud-filestore-log-troubleshooting:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/google-cloud-filestore-log-troubleshooting &&
cp -R "$tmp/skills/cloud/google-cloud-filestore-log-troubleshooting" ~/.copilot/skills/google-cloud-filestore-log-troubleshooting &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/google-cloud-filestore-log-troubleshooting inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/google/skills.git

Then copy skills/skills/cloud/google-cloud-filestore-log-troubleshooting into your agent's skills folder as google-cloud-filestore-log-troubleshooting. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Google cloud filestore log troubleshooting FAQ

How do I install Google cloud filestore log troubleshooting in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/google-cloud-filestore-log-troubleshooting to use it in all your projects, or to .claude/skills/google-cloud-filestore-log-troubleshooting in one project.

Does Google cloud filestore log troubleshooting run scripts?

Yes. It runs Python scripts. No network calls were found in its scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Google cloud filestore log troubleshooting?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Google cloud filestore log troubleshooting?

The closest alternatives to Google cloud filestore log troubleshooting are Gem devops guidelines, Azure logic apps standard CLI, Azure container registry CLI, Azure devops CLI and Terraform azurerm set diff analyzer.

More from google/skills

  1. Google platform decision and setup guidance, loaded on demand from Google's skill catalog

    • Open source
    • 24.4K GitHub stars
  2. Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services an

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  3. Provides expert guidance on Identity and Access Management (IAM) and authenticating and authorizing to Google Cloud services and APIs, cover

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  4. Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resour

    • Open source
    • 24.4K GitHub stars
    • Cloud and infrastructure
  5. Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter,

    • Open source
    • 24.4K GitHub stars
  6. Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its

    • Open source
    • 24.4K GitHub stars

Alternatives to Google cloud filestore log troubleshooting

  1. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  2. Create, inspect, validate, test, run, debug, package, and deploy Azure Logic Apps Standard projects using the Azure CLI logicapp extension

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  3. Manage Azure Container Registry via the az acr CLI including registries, images, cloud builds, ACR Tasks, authentication, tokens, geo-replic

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoi

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  5. Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attribut

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  6. Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permi

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure