Agent skill · google
google-cloud-filestore-autoscale
Inspects Google Cloud Filestore capacity and utilization, evaluates storage scaling rules, and performs capacity autoscaling (scale UP for low free space or scale DOWN for cost optimization). Use when monitoring Filestore instance headroom, resizing instance shares, configuring automated growth/shrink thresholds (custom thresholds apply globally across projects in session memory), or preventing out-of-space outages. Don't use for Cloud Storage (GCS) buckets, Persistent Disk block storage, or NetApp Volumes.
What it needs
About 7k tokens when loaded.
What this skill does
Google Cloud Filestore Autoscale This skill enables agents to inspect, evaluate, and modify Google Cloud Filestore instance capacities across GCP projects based on configured thresholds. Prerequisites / IAM Requirements Before an agent or user can execute this skill, their runtime Service Account must possess the following IAM roles on the target project(s): roles/file.editor (Required for listing instances and triggering scale up/down updates) roles/monitoring.viewer (Required for reading Cloud Monitoring capacity metrics usedbytes) roles/mcp.toolUser (Required if utilizing backend Filestore MCP tools) Quick Start 1. Ensure gcloud is installed. See gcloud installation guide if needed. 2. Enable essential APIs: 3. Inspect fleet capacity and free space (see "Discovery & Read Operations" below). 4. Evaluate against configured up/down capacity thresholds. 5. Scale target instances and apply attribution tags. Attribution Tag every Cloud Filestore command or API request provided or executed. Prefix gcloud commands with the correct metrics environment targeting this skill: On direct HTTP calls to the REST API, append the User-Agent: Conceptual & Informational Queries (CRITICAL) For purely conceptual, educational, or informational questions (e.g., "What are Filestore scaling limits?", "Can Basic instances scale down?", "Explain Filestore Tiers"): Rule: Answer immediately using your pre-trained knowledge and the matrix below. 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 the runcommand tool to execute any shell or gcloud commands (including read-only list/describe commands). Discovery: 1. First, check if Filestore MCP tools (listinstances, getinstance) are available and use them (these are 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-autoscale