Google Cloud Recipe Onboarding
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, non-interactive path for individual developers to set up their Google Cloud environment. It automates the verification of local tooling, authentication, project creation, and billing linkage. Designed for personal or trial accounts, it includes safety guardrails to prevent enterprise-level configuration errors and ensures all actions are performed with explicit user consent.
What it does
- Verifies local gcloud CLI installation and authentication status.
- Audits existing Google Cloud projects to prevent duplicate creation.
- Creates new projects with automated collision handling for project IDs.
- Links projects to active billing accounts to enable resource deployment.
- Provides a structured consent gate before executing any infrastructure mutations.
- Validates the final environment state to ensure successful configuration.
When to use it
- When a new developer needs to set up their first Google Cloud project.
- When you need to verify if a local machine is ready for Google Cloud development.
- When you need to link a new project to an existing billing account.
- When you want a safe, step-by-step process to initialize a cloud workspace.
Advantages
- Prevents accidental creation of duplicate projects.
- Ensures deterministic, machine-parseable outputs using CLI flags.
- Includes built-in safety checks to avoid enterprise-level configuration.
- Provides clear, step-by-step guidance with mandatory user consent gates.
Usage examples
- “I want to get started with Google Cloud.”
- The agent audits your local environment, checks your authentication, and asks if you would like to reuse an existing project or create a new one.
- “Create a new Google Cloud project for my app.”
- The agent prompts for a project name, presents a summary table of the configuration, and waits for your explicit confirmation before creating the project and linking billing.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/google-cloud-recipe-onboarding/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip google-cloud-recipe-onboarding.zip -d .agents/skills
Documentation by Google
Onboarding to Google Cloud
This skill provides a streamlined, non-interactive "happy path" for a singleton developer to get started with Google Cloud. It covers everything from environment verification and authentication to project selection, billing account linkage, and downstream safety chaining.
Attribution
For all gcloud CLI, REST API, and MCP attribution requirements when executing
commands with this skill, follow the instructions in
Usage Attribution.
[!IMPORTANT] For autonomous agents executing this skill:
Check-Before-Mutate Audits: Always perform silent pre-execution state audits prior to proposing or executing any project or billing changes.
Single-Question Policy: Ask the user for exactly one operational parameter or confirmation at a time during interactive execution.
Non-Interactive Output: Append non-interactive overrides (
--quiet,--format="json") to all mutation commands to guarantee deterministic, machine-parseable outputs and prevent terminal hangs.First Turn Interaction Rules (Trigger Turn): When the developer first triggers this skill with a general onboarding request (e.g. says "I want to get started with Google Cloud"):
Preamble Guidance: Proactively include a short orienting preamble guiding the developer to create a Google Cloud account (pointing to the console at
https://console.cloud.google.com/) and rungcloud auth loginto authorize their workstation, even if they appear to be already logged in.First Turn Single-Question: Perform pre-flight audits silently, but do not present a complete parameters summary table or ask for final consent in the first turn. Instead, ask the developer exactly one initial operational question (e.g., "Would you like to reuse an existing active project, or create a brand new one?"). Note: If the developer's initial prompt explicitly states "I approve the onboarding configuration", "Let's proceed with onboarding", or requests a dry-run plan (e.g., "Show me the exact plan or dry-run commands"), bypass the general preamble and initial question, and proceed directly to the requested step.
Overview
For an individual developer, onboarding to Google Cloud involves verifying local terminal tools, establishing an authenticated session, selecting or instantiating a workspace (Project), and linking it to an active billing account. Google Cloud offers a Free Tier and a Free Trial with $300 in credits for first-time users. Learn more here.
Prerequisites
A personal Google Account (e.g.,
@gmail.com) or Google Workspace / Cloud Identity account.A valid payment method (credit card or bank account) required for identity verification and to activate the $300 Free Trial credit introduced in the Overview.
Steps
Section 1: Verify Host Tooling Setup
Before soliciting input or proposing mutations, silently audit the host system's active tooling and environment status.
Check if the
gcloudCLI binary is installed and accessible:which gcloudCheck if there is an active authenticated identity session:
gcloud auth list --format="json"If the pre-execution audit for
which gcloudreturns a valid path, proceed directly to Section 2: Authenticate and Route Session.If the binary is missing, halt execution and direct the agent to install gcloud using the gcloud skill. Provide the official Google Cloud CLI Installation Guide to the developer for steps to set up authentication.
Section 2: Authenticate and Route Session
Authorize the gcloud CLI to access Google Cloud using the developer's Google Account, and verify that the account is appropriate for standalone developer onboarding.
Execute Credentials Authentication:
gcloud auth login[!IMPORTANT] New User / Unauthenticated Guidance: If the pre-execution state audits or command failures confirm that the developer is unauthenticated (e.g.,
gcloud auth listis empty or active credentials are missing):Guide them to create a Google Cloud account by navigating to the Google Cloud Console.
Instruct them to execute the
gcloud auth logincommand to authorize their local workstation terminal session.Do not attempt project creation or resource configuration until authentication is completed successfully.
Verify Active Identity:
gcloud config get-value account --format="json"Programmatic Enterprise Routing Guardrail: Before proceeding, verify if the account is bound to a corporate organization, as enterprise setups must follow a different architecture:
gcloud organizations list --format="json"Note that new Free Trial accounts automatically receive a Self-Owned Organization (SOO). To distinguish between a personal Free Trial account and an enterprise organization, inspect the JSON output:
Enterprise Organization (Halt Execution): If the output list contains an organization node where
owner.directoryCustomerIdis present (confirming a domain-verified Google Workspace or Cloud Identity organization), or if the user's prompt explicitly mentions corporate landing zones or multi-tenant project structures:Halt execution of this skill immediately.
Route the developer to the official Google Cloud Setup guided flow.
Personal Account / Free Trial SOO (Proceed): If the output list is empty
[], or if it contains a Self-Owned Organization (whereowner.directoryCustomerIdis absent anddisplayNameis not a verified domain name), proceed to Section 3: Select or Instantiate Your Google Cloud Project.
Section 3: Select or Instantiate Your Google Cloud Project
Google Cloud resources are organized into Projects. When developers sign up for a Free Trial via the console, Google Cloud automatically creates a default project (e.g., "My First Project"). Always audit the active environment first to reuse existing projects and prevent token-burning collision errors.
Silent Project Discovery: List active, accessible projects (limited to prevent context window overflow):
gcloud projects list --filter="lifecycleState=ACTIVE" --limit=20 --format="json"Reuse Existing Project (Recommended): If the list returns an active project, present it to the developer and propose setting it as the default working project:
gcloud config set project {PROJECT_ID} --quietCreate Custom Project: If no projects exist, or if the developer explicitly requests a brand new workspace:
Solicit a custom
PROJECT_IDandPROJECT_NAMEfrom the developer (Single-Question Policy).Structured Confirmation & Consent Gate (Mandatory): Before running any project creation or billing linkage commands, the agent must present a structured markdown table summarizing the target parameters:
Parameter Value Target Project ID {PROJECT_ID}Target Project Name {PROJECT_NAME}Active Identity Account {ACCOUNT}Target Billing Account ID {BILLING_ACCOUNT_ID}Ask the user the exact consent query:
"I am ready to initialize your Google Cloud project and link billing. Do you want me to proceed?"CRITICAL: The agent MUST NOT execute any
gcloud projects createor billing link commands during this turn. You must display this table, ask the exact consent query, and strictly stop to wait for the user's positive affirmation.Project ID Collision Suffix Recovery: If the project creation command fails because the
PROJECT_IDis already taken globally (returning aPROJECT_ID_COLLISIONorALREADY_EXISTSerror):Automatically append a random 4-digit suffix (e.g., changing
my-projecttomy-project-8472).Propose this new available project ID to the developer and re-solicit consent before retrying.
Execute Project Creation: Once explicit user consent is confirmed:
gcloud projects create {PROJECT_ID} --name="{PROJECT_NAME}" --quiet --format="json"Set the active working project:
gcloud config set project {PROJECT_ID} --quiet
Section 4: Verify and Link Billing
To deploy resources on Google Cloud, your project must be linked to an active Cloud Billing account.
Audit Billing Status: Check if the active project is already linked to a billing account:
gcloud billing projects describe {PROJECT_ID} --format="json"If the output contains
"billingEnabled": true, skip linkage and proceed immediately to Section 5: Skill Chaining (Spend Controls & Workloads).Discover Available Billing Accounts: If the project is unlinked, query the available billing account handles linked to the authenticated user identity:
gcloud billing accounts list --format="json"Link Billing Account: Propose linking the project to the discovered Billing Account ID, and execute:
gcloud billing projects link {PROJECT_ID} --billing-account={BILLING_ACCOUNT_ID} --format="json"
Section 5: Skill Chaining (Spend Controls & Workloads)
Onboarding setup is now complete. To safeguard your environment and deploy workloads, you can chain to downstream specialized skills:
Billing Spend Controls: To avoid accidental cost overruns, consider setting up a programmatic control to automatically disable billing. When billing is disabled, all Google Cloud services and usage in the project are terminated to stop further costs:
Direct the developer to the official Disable Billing Usage with Notifications Guide, which provides detailed instructions on how to automatically shut down billing when costs exceed the project budget.
Deploy Workloads: To deploy your first resource, trigger the downstream specialized skill matching your target application (e.g., cloud-run-basics or
bigquery-basics). If the specialized skill is not locally available, direct the developer to the corresponding official quickstart, such as the Cloud Run Container Deployment Quickstart. Note: Those downstream specialized skills are individually responsible for dynamically enabling their own required service APIs (e.g., run.googleapis.com) inline during execution.
Validation Logic
After completing the onboarding steps, programmatically verify the completed environment state using these diagnostic commands:
Verify CLI Installation:
which gcloudVerify Authenticated Identity:
gcloud config get-value accountVerify Project Workspace Existence:
gcloud projects describe {PROJECT_ID} --format="json"Verify Billing Linkage (Ensure the JSON output contains
"billingEnabled": true):gcloud billing projects describe {PROJECT_ID} --format="json"
Additional Resources
Usage Attribution: Standardized usage attribution tags for
gcloudCLI, REST API, and MCP requests.
Files
- ATTRIBUTION.mdAdded by AutoGineer878 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md12.8 KiB
- references/attribution.md1.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.
Needs: Needs a command-line tool, Needs Node.js
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-recipe-onboarding · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- google/skills
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-recipe-onboarding.zip