Google Cloud Filestore Autoscale
GoogleOfficialPublished by Google
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured workflow for monitoring and managing Google Cloud Filestore capacity. It enables agents to inspect instance utilization, evaluate storage against defined thresholds, and execute scaling operations. The skill supports both scale-up actions for low-headroom instances and scale-down actions for cost optimization, while strictly adhering to tier-specific constraints and safety requirements.
What it does
- Discovers Filestore instances across Google Cloud projects.
- Queries project-wide storage utilization metrics via Cloud Monitoring.
- Calculates free space percentages to determine scaling requirements.
- Evaluates instances against safety thresholds for automated scaling.
- Generates attributed gcloud commands for capacity adjustments.
- Provides a summary report of instance health and recommended actions.
When to use it
- When monitoring Filestore instance headroom to prevent out-of-space outages.
- When identifying opportunities to reduce costs by scaling down underutilized instances.
- When configuring automated growth or shrink thresholds for storage resources.
- When performing routine capacity audits across a fleet of Filestore instances.
Advantages
- Prevents manual errors by enforcing tier-specific scaling constraints.
- Optimizes cloud storage costs through automated downscaling recommendations.
- Ensures operational safety with mandatory user confirmation before execution.
- Maintains auditability by requiring attribution tags on all API and CLI requests.
Usage examples
- “Check the status of my Filestore instances in project my-gcp-project and suggest scaling actions.”
- The agent will list all instances, calculate their current utilization, and present a table showing which instances require scaling, along with the specific gcloud commands to perform the updates.
- “Are there any Filestore instances I can scale down to save costs?”
- The agent will identify instances with high free space that support downscaling, verify they are above their minimum capacity floor, and propose a target capacity with estimated savings.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-filestore-autoscale/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-filestore-autoscale.zip -d .agents/skills
Documentation by Google
Filestore Autoscale
This skill enables agents to inspect, evaluate, and modify Filestore instance capacities across Google Cloud 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 metricsused_bytes)roles/mcp.toolUser(Required if utilizing backend Filestore MCP tools)
Quick Start
Ensure
gcloudis installed. See gcloud installation guide if needed.Enable essential APIs:
gcloud services enable file.googleapis.com monitoring.googleapis.com --quietInspect fleet capacity and free space (see "Discovery & Read Operations" below).
Evaluate against configured up/down capacity thresholds.
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:
CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-autoscale)" \
gcloud filestore instances update ...On direct HTTP calls to the REST API, append the User-Agent:
User-Agent: gcs-skills/1.0 (skill:google-cloud-filestore-autoscale)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
run_commandtool to execute any shell orgcloudcommands (including read-only list/describe commands).Discovery:
First, check if Filestore MCP tools (
list_instances,get_instance) are available and use them (these are API calls, not command executions).If MCP tools are not available, search local markdown documentation files (e.g.,
references/instance-tiers-specs.md) for any mock instance definitions or project details matching the request. (Do NOT attempt to read evaluation config files such asEVAL.yamlorEVAL.txtpbduring evaluation runs as access is restricted).If no data can be found, explain the required steps and formulas, and output the exact commands the user should run, without executing them yourself.
Mandatory User Confirmation Requirement: Even when the user prompt asks not to execute commands or asks only for command syntax/recommendations, your response MUST STILL end with a clear question prompting the user for confirmation before executing any capacity resizing commands (e.g., "Would you like me to proceed with scaling
[instance]from [A] TiB to [B] TiB? Please confirm to execute.").
Tier & Capacity Limits Matrix
Filestore tiers enforce specific boundaries and behaviors. The skill must accept both modern UI names (Basic, Zonal, Regional) and legacy API enums interchangeably.
See references/instance-tiers-specs.md for the full Tier & Capacity Limits Matrix (Min/Max capacities, step increments).
Critical Thresholds:
Basic HDD / Basic SSD: Can scale up, but cannot scale down.
Zonal / Regional: Can scale down, but cannot shrink below their minimum floor (1 TiB or 10 TiB depending on band) AND cannot shrink below the current
used_bytesmetric.
Core Operational Workflow
1. Discovery & Read Operations
Step 1 (Fleet Discovery): Call the MCP tool
list_instances(parent='projects/{project_id}/locations/-')or CLIgcloud filestore instances list --project={project_id}to discover all Filestore instances in the target project. Read thecapacityGbandtierdirectly from the instances returned.Step 2 (Single Bulk Utilization Metric Query): Immediately after discovering instances, query the Cloud Monitoring API for the
file.googleapis.com/nfs/server/used_bytesmetric across the entire project in a single request (seereferences/monitoring-metrics.mdfor runtime-specific options including GCP REST API,gcloud,curl, and MCP tools).CRITICAL: Make exactly ONE bulk metric request for the entire project. NEVER emit multiple per-instance queries or loops. Do NOT filter by zone or region.
Step 3 (Metric Extraction & Calculation):
Match each instance's short name (or
resource.labels.instance_name/metric.labels.instance_name) in the returnedtimeSeriesdata to extract its latestint64Valuebytes.If an instance is not listed in
timeSeriesor has no points, default itsused_bytesto 0.Calculate
used_bytes_gb = used_bytes / (1024^3).Calculate
Free Space % = ((capacityGb - used_bytes_gb) / capacityGb) * 100.NEVER leave
Used BytesorFree Space %as "N/A". Populate actual numbers into the output summary table.
2. Autoscale Needed Matrix
The skill must categorize each evaluated instance into one of 5 definitive verdicts. On the initial analysis/fleet inspection run, the skill suggests the required scaling action with target capacity and update commands, and prompts for user confirmation before executing any autoscale modifications. State the value of the "Autoscale Needed" column clearly as one of the following:
Yes (Scale Up): Triggered when free space percentage is below the scale-up safety threshold (< 15% free space remaining). The evaluation response MUST explicitly state that the current free space percentage is below the 15% scale-up safety threshold. Capacity must be increased by 10% (default) or step-size minimum, rounded to the tier's step increment (256 GiB for Small Band [1–9.75 TiB], 2.5 TiB for Large Band [10–100 TiB], as specified in
references/instance-tiers-specs.md), not exceeding the maximum capacity. Suggest target capacity, provide the attributedgcloudupdate command, and MUST conclude the response with a clear question prompting the user for confirmation to execute (e.g., "Would you like me to proceed with scaling[instance]from [A] TiB to [B] TiB? Please confirm to execute.").Yes (Scale Down): Triggered when free space exceeds the scale-down threshold (> 30% free space remaining) and the instance is eligible for downscaling (Zonal or Regional / Enterprise tiers). Apply the default step reduction of -10% of current capacity, aligned to the tier's step increment (256 GiB for Small Band [1–9.75 TiB], 2.5 TiB for Large Band [10–100 TiB], as specified in
references/instance-tiers-specs.md). For example, for a 2 TiB (2048 GiB) Enterprise / Regional instance, rounding to the 256 GiB step yields a proposed target capacity of 1.75 TiB (1792 GiB, or 1.8 TiB). The response MUST explicitly verify that the proposed target capacity (e.g. 1.75 TiB / 1792 GiB or 1.8 TiB) remains strictly above both the tier's minimum capacity floor (e.g. 1 TiB for Enterprise / Small Band, 10 TiB for Large Band) and currently used space (e.g. 0.9 TiB). Do NOT reduce directly to the floor in a single step. Suggest target capacity, estimated cost savings, provide the attributedgcloudupdate command, and prompt the user for confirmation to execute.No (Healthy): Triggered when the instance's free space is within the optimal operating range (15% – 30%). No action required.
No (At min capacity limit): Triggered when free space is > 30%, but the instance is already at the minimum allowed tier capacity floor (e.g. 1 TiB for Small Band or 10 TiB for Large Band) or currently used space limit. No action can be taken.
No (Tier cannot scale down): Triggered when free space is > 30%, but the instance is on a Basic tier (Basic HDD / Basic SSD) which does not support downscaling. The agent must explicitly inform the user that scale-down is not supported and suggest data migration instead. No action can be taken.
Output Format
Every status report, evaluation, or recommendation response MUST include a markdown table summarizing the evaluated instances. Even if evaluating a single instance, format it as a table. The table MUST contain the following columns:
InstanceService TierProvisioned CapacityUsed BytesFree Space %Autoscale Needed(MUST contain one of:Yes (Scale Up),Yes (Scale Down),No (Healthy),No (At min capacity limit), orNo (Tier cannot scale down))
Example standard output table:
| Instance | Service Tier | Provisioned Capacity | Used Bytes | Free Space % | Autoscale Needed | Proposed Action |
|---|---|---|---|---|---|---|
| `[instance-name]` | REGIONAL | 2048 GiB | 900 GiB | 56.05% | Yes (Scale Down) | Scale down to 1792 GiB. `CLOUDSDK_METRICS_ENVIRONMENT=... gcloud filestore instances update ...` |3. Execution & Confirmation Workflow
Analysis & Recommendation (First Run / Inspection):
Calculate step-aligned target capacity adhering to tier ceilings, floors, and basic scale-up only rules.
Present the summary table and proposed actions.
MANDATORY USER CONFIRMATION PROMPT: Whenever recommending target capacity or providing a
gcloud filestore instances updatecommand, your response MUST explicitly include a clear question asking the user to confirm execution before any modifications are made (e.g. "Would you like me to proceed with scaling[instance]from [A] TiB to [B] TiB? Please confirm to execute.") to prevent accidental billing spikes or capacity exhaustion.Do not execute autoscale commands without user confirmation.
Execution upon Confirmation:
Once the user confirms (e.g., "Yes, proceed with scaling", "Scale instance X"), execute the attributed
gcloud filestore instances updatecommand on the confirmed instance(s).
Fallback:
If execution fails due to Prod mutation restrictions, output the failure reason and provide the user with the exact attributed
gcloudcommand to run manually, reminding them to confirm before manual execution.
Custom Thresholds
When the user configures or passes custom threshold values in prompts (e.g. "Scale up if free space drops below 10% with a 20% step", or custom max_threshold / up_increment):
Global Session Memory Confirmation: The response MUST accept and acknowledge the custom thresholds and MUST explicitly confirm that custom thresholds apply globally across projects in session memory, explicitly mentioning the target project IDs evaluated or active in session memory to prevent accidental cross-project misconfiguration.
Configuration Summary: The response MUST display the updated active configuration summary showing all active thresholds and step increments.
Preserve Overrides: The response MUST NOT revert to default thresholds (15% / 10%) when custom overrides are provided.
Reference Directory
For progressive disclosure of deeper topics, consult the references/ directory:
Files
- ATTRIBUTION.mdAdded by AutoGineer882 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md12.3 KiB
- references/instance-tiers-specs.md2.8 KiB
- references/monitoring-metrics.md3.3 KiB
- references/troubleshooting-errors.md1.6 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/google-cloud-filestore-autoscale · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google or Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-filestore-autoscale.zip