agentsclimarketplace
Sign in

Google cloud recipe onboarding

Skill jmxt3/gitscape.ai/.agents/skills/google-cloud-recipe-onboarding

Guidance for a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resource.From its SKILL.md

Install
npx -y skills add jmxt3/gitscape.ai --skill google-cloud-recipe-onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • skips confirmationTells the agent to proceed without asking first, 1 time: "--quiet".
  • runs commandsInstructs the agent to run 5 commands, including `gcloud init` and 4 more.
  • fetches URLsInstructs the agent to fetch 1 URL, including https://cloud.google.com/sdk/docs/install.

SKILL.md

5.7 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Onboarding to Google Cloud

This skill provides a streamlined "happy path" for a singleton developer to get started with Google Cloud. It covers everything from initial account setup to deploying your first cloud resource.

Overview

For an individual developer, onboarding to Google Cloud involves establishing a personal identity, setting up a billing method, and creating a workspace (Project) where resources can be managed. Google Cloud offers a Free Tier and Free Trial for multiple products. Learn more here.

Clarifying Questions

Before proceeding, the agent should clarify the user's current status:

  1. Do you already have a Google Account (Gmail or Google Workspace)?
  2. Are you looking to set up a personal account for learning/experimentation, or are you part of an organization with existing infrastructure?
  3. Are you an IT admin within a larger enterprise, setting up Google Cloud for your organization?
  4. What is the first type of resource or application you are interested in building (e.g., a website, a data pipeline, a virtual machine)?
  5. Do you prefer to use the command line (CLI), an IDE (e.g. VSCode, Antigravity), or do you prefer using the web-based Google Cloud console?

Prerequisites

  • A Google Account (e.g., @gmail.com).
  • A valid payment method (credit card or bank account) for billing verification (even for the free trial).

Steps

1. Sign Up and Activate Free Credit

  1. Go to the Google Cloud Console.
  2. Sign in with your Google Account. This will "Activate" your $300 free credit.

2. Create Your First Google Cloud Project

Google Cloud resources are organized into Projects.

  1. In the Google Cloud console, click the project picker dropdown at the top of the page.
  2. Click New Project.
  3. Enter a Project Name (e.g., my-first-gcp-project).
  4. Note the generated Project ID; you will use this for CLI and API interactions.
  5. Click Create.

3. Set Up Billing

Ensure your project is linked to your Free Trial Cloud Billing account.

  1. Go to the Billing section in the console.
  2. Confirm that your new project is listed under "Projects linked to this billing account."

4. Install and Initialize the Google Cloud CLI

The Google Cloud CLI (gcloud CLI) is the primary tool for interacting with Google Cloud from your local machine.

  1. Download and install the Google Cloud CLI.
  2. Open your terminal and run: gcloud init
  3. Follow the prompts to log in and select your project.

5. Enable Necessary APIs

Most services require their specific API to be enabled before use. For example, to use Cloud Run, run: gcloud services enable run.googleapis.com

Note that some Google Cloud APIs, including Cloud Logging, are enabled by default.

6. Deploy Your First Resource

Choose a simple entry point based on your needs:

  • Cloud Run (Recommended for Apps): Deploy a containerized "Hello World" app.
  • Compute Engine: Create a small Linux VM (e.g., e2-micro which is part of the Always Free tier in certain regions).
  • Cloud Storage: Create a bucket to store files.

Example (Cloud Run):

    gcloud run deploy hello-world \
    --image=gcr.io/cloudrun/hello \ --platform=managed \ --region=us-central1 \
    --allow-unauthenticated --quiet

This command will output a public URL, that you can reach in a web browser. Congrats - you just deployed your first Google Cloud resource!

7. Next Steps

Validation Logic

Use this logic to determine if the user has successfully completed the Google Cloud onboarding process:

  • Project Created: Does the user have a Project ID?
  • Billing Linked: Is the project associated with a billing account (check via gcloud beta billing projects describe PROJECT_ID)?
  • CLI Authenticated: Does gcloud config list show the correct account and project?
  • Resource Verified: Can the user access the URL or IP of the deployed resource?

What ships with it: 1 file

5.5 KB alongside SKILL.md

reference/

Gives 0 of the 12 instructions most codebase onboarding skills give in ~1.3k tokens

Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06

  • Focus first session on one successful outcomein 34 of 307, across 15 files
  • Show progress and celebrate completionsin 32 of 307, across 13 files
  • Prefer interactive doing over tutorialsin 32 of 307, across 13 files
  • Remove every step between signup and core valuein 32 of 307, across 13 files
  • Keep checklists to 3-7 items ordered by valuein 32 of 307, across 13 files
  • Read product marketing context before asking questionsin 28 of 307, across 13 files
  • Focus fixes on the biggest funnel drop-offsin 22 of 307, across 7 files
  • Define activation as the action most correlated with retentionin 20 of 307, across 6 files
  • Give one clear next action at every stepin 19 of 307, across 8 files
  • Understand product context and current state before recommendingin 15 of 307, across 3 files
  • Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
  • Trace one request from entry to responsein 14 of 307, across 8 files

Said here and by no other author read

  • Sign in to the Google Cloud console
  • Create a new project
  • Note the generated project ID
  • Link the project to a billing account
  • Confirm the project appears under the billing account
  • Install the Google Cloud CLI

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.