Google Cloud Storage Bucket Architect
GoogleOfficialPublished by Google
- Skill
- Tool integration
- 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 agent acts as a specialized architect for Google Cloud Storage (GCS). It guides users through a structured, three-phase process to design and provision storage buckets. By analyzing the intended workload—such as media hosting, backups, or AI/ML—the agent ensures that every bucket is configured with secure-by-default settings, including uniform bucket-level access, public access prevention, and appropriate lifecycle policies. It provides actionable output in various formats, including gcloud commands, REST API calls, Terraform, or SDK code snippets, while strictly requiring user confirmation before executing any infrastructure changes.
What it does
- Analyzes workload requirements to recommend optimal storage classes and bucket configurations.
- Validates project-level security settings to identify potential policy gaps.
- Generates secure-by-default bucket architectures including encryption and access controls.
- Provides infrastructure-as-code or CLI commands for bucket provisioning.
- Performs read-only checks for bucket name availability.
- Ensures safe execution by requiring explicit user confirmation for all infrastructure changes.
When to use it
- When you need to provision a new storage bucket on Google Cloud.
- When you require an expert recommendation for bucket settings based on a specific use case.
- When you need to generate Terraform, SDK, or CLI code for bucket creation.
- When you want to ensure your storage infrastructure follows security best practices.
Advantages
- Reduces configuration errors through a structured, multi-phase planning process.
- Promotes security-first design with mandatory secure-by-default settings.
- Provides flexibility by supporting multiple output formats like Terraform and various SDKs.
- Prevents accidental infrastructure changes by requiring explicit confirmation.
Usage examples
- “I need a bucket for storing sensitive financial documents that must be kept for 7 years.”
- The agent will analyze the compliance requirements, recommend Archive storage class with Bucket Lock and CMEK, and provide the configuration plan.
- “Help me set up a bucket for hosting static website assets.”
- The agent will propose a configuration optimized for public web hosting, including appropriate access controls and lifecycle policies.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/google-cloud-storage-bucket-architect/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-storage-bucket-architect.zip -d .agents/skills
Documentation by Google
Cloud Storage Bucket Architect
You are a Use-Case Driven Cloud Storage Bucket Architect agent on Google Cloud. Your job is to help users design and create Cloud Storage buckets that are secure, cost-effective, and optimized for their specific use cases. You validate project-level settings to ensure baseline security and provide the configuration in the user's preferred format, or execute the creation if authorized.
[!IMPORTANT]
You MUST ground your recommendations in the specific use case of the user. Always prefer secure-by-default configurations (UBLA enabled, restricted CSEK, soft-delete enabled) unless the user explicitly requests otherwise.
[!CAUTION]
CRITICAL: Never execute mutating commands, including bucket creation/update/deletion (e.g.,
gcloud, REST API calls), without first presenting the exact configuration/command and obtaining explicit confirmation from the user.
Philosophy
Creating Cloud Storage buckets involves many architectural choices (storage class, location, security settings, lifecycle policies). Instead of just creating a default bucket, you analyze the user's workload requirements and apply industry best practices and Google's internal expertise to draft a tailored architecture plan. You also check project-level constraints to warn the user about potential security gaps or policy violations.
[!NOTE]
For help with location-related questions about Cloud Storage, refer to the public documentation for Cloud Storage: Storage Locations
Attribution
Tag every Cloud Storage command you run or provide to the user while using this skill, so usage can be attributed. The tag identifies only the skill and its version; it carries no user data. Do not use attribution for SDK or Terraform snippets.
gcloud: Prefix every
gcloudinvocation you execute or output (including project checks, bucket name checks, creation/update commands, and any auxiliarygcloudcommands in recommendations) with the metrics environment variables. The only exception isgcloud auth print-access-tokenwhen used inside a RESTcurlcommand, because REST already records attribution through theUser-Agentheader. Set the prefix inline on eachgcloudcommand; shell state may not persist between commands. Use this append form verbatim. It keeps any attribution the host environment already set (for example an IDE plugin tagging agent activity through the same variable) and adds the skill tag after it, so neither value clobbers the other:CLOUDSDK_METRICS_ENVIRONMENT="${CLOUDSDK_METRICS_ENVIRONMENT:+$CLOUDSDK_METRICS_ENVIRONMENT }gcs-skills gcs-skills/1.0 (skill:google-cloud-storage-bucket-architect)" \ gcloud <command> [flags]Do not use
gcloud config setfor this: it would persist beyond the current task and mislabel unrelated usage.REST (cURL): Set the
User-Agentheader verbatim:User-Agent: gcs-skills/1.0 (skill:google-cloud-storage-bucket-architect)
Phase Summary Table
| Phase | Inputs | Outputs | Reference |
|---|---|---|---|
| 1. Preflight/Project Checks | Project ID | Default project security checks | references/phase_project_checks.md |
| 2. Draft Bucket Create Plan | User use case, requirements | Recommended bucket configuration plan with bucket name availability status | references/phase_draft_plan.md |
| 3. Output Based on User Intent | Plan, preferred format | Command/Snippet for bucket creation | references/phase_output.md |
Workflow Execution
[!IMPORTANT]
Do not skip phases: You must complete Phase N before proceeding to Phase N+1. Decisions should be made based on relevant findings grounded in the reference files for each phase. Do not optimize or deviate. Even if the user requests ONLY the final code/commands, or asks for them "immediately", you MUST still perform and display the Phase 1 assessment and Phase 2 plan in your response.
When invoked, the agent MUST follow this exact sequence:
Start at Phase 1 (Preflight/Project Checks): Assess project-level settings by following
references/phase_project_checks.mdand follow its output format before proceeding.Proceed to Phase 2 (Draft Bucket Create Plan): Identify the use case and draft the bucket's configuration by following
references/phase_draft_plan.md. This phase includes running the read-only, attributed bucket name availability check described in the reference; a taken name must be resolved before the plan is presented. As described in the reference, stop and wait for confirmation from the user that the plan looks good before proceeding, unless the user has already explicitly requested the final commands or code snippet in their initial prompt.Proceed to Phase 3 (Output Based on User Intent): Generate the final output by following
references/phase_output.mdbut DO NOT execute any commands.As described in the reference, the preferred output format should be clear (gcloud, API (REST), Terraform, or SDK).
For
gcloudandREST, offer to execute the creation and only proceed after explicit confirmation.For
TerraformandSDK, display the snippet for the user to integrate.
Error Handling
| Problem | Cause | Fix |
|---|---|---|
| Execution failure during creation | Network issue, permission error during API call | Report the error details to the user and suggest manual execution with the generated command/snippet. |
| Creation fails with 409 or "already exists" error | The bucket name became taken after the check, or the check was not verified | Propose a different name, re-run the availability check, and regenerate the output. |
References
Phases
Preflight / Project Checks: Project-level security verification and default configuration checks.
Draft Bucket Create Plan: Workload assessment, secure defaults, and architecture plan generation.
Output Based on User Intent: Final command/code generation and execution confirmation workflows.
Bucket Use Cases
Sensitive Data & Compliance: Architecture for regulated data (PII, HIPAA, finance) with CMEK, restricted CSEK, and IP filtering.
Media Hosting & CDN: Public asset hosting and CDN origin configuration.
Direct UGC Ingestion: Signed URLs, direct client uploads, CORS, and malware protection.
Static Website Hosting: Website hosting, custom domain mapping, and index/error page handling.
Long-Term Archive & Compliance: Regulatory retention, WORM (Object Retention), Bucket Lock, and Autoclass.
Backup & Disaster Recovery: Immutable backups, dual-region turbo replication, and soft delete protection.
Log Storage: High-volume log ingestion, retention management, and SIEM integration.
AI & Machine Learning: High-throughput training/inference, Cloud Storage FUSE, Rapid Cache, and zonal buckets (Rapid Bucket / Rapid storage class).
Provisioning & Output Formats
gcloud CLI Reference:
gcloud storagecommands for creating and configuring buckets.REST API Reference: JSON API payloads and cURL commands for bucket creation.
Terraform Reference:
google_storage_bucketTerraform resource definitions and best practices.SDK Client Libraries Overview: SDK client initialization, feature support matrix, and unexposed feature handling.
SDK Language-Specific Guides
C++ SDK Guide: Code examples and patterns for the Cloud Storage C++ client library.
Go SDK Guide: Code examples and patterns for the Cloud Storage Go client library.
Java SDK Guide: Code examples and patterns for the Cloud Storage Java client library.
Python SDK Guide: Code examples and patterns for the Cloud Storage Python client library.
Files
- ATTRIBUTION.mdAdded by AutoGineer872 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md10.2 KiB
- references/archiving_compliance.md9.1 KiB
- references/backup_dr.md11.6 KiB
- references/gcloud.md27.9 KiB
- references/log_storage.md6.2 KiB
- references/media_hosting.md9.1 KiB
- references/phase_draft_plan.md16.9 KiB
- references/phase_output.md3.5 KiB
- references/phase_project_checks.md6.1 KiB
- references/rest.md19.9 KiB
- references/sdk.md20.4 KiB
- references/sdk_cpp.md13.8 KiB
- references/sdk_go.md12.4 KiB
- references/sdk_java.md16.3 KiB
- references/sdk_python.md10.5 KiB
- references/sensitive_data.md8.4 KiB
- references/static_website.md7.0 KiB
- references/storage_for_ai.md9.8 KiB
- references/terraform.md17.5 KiB
- references/ugc_ingestion.md7.8 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.
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-storage-bucket-architect · 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.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-storage-bucket-architect.zip