google-cloud-onboarding
Guides developers through their first steps on Google Cloud, covering account creation, billing setup, project management, CLI installation, and deploying a first resource.
What this skill does
# Onboarding to Google Cloud
This skill provides a streamlined "happy path" for a singleton developer to get
started with [Google Cloud](https://cloud.google.com/). 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](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy#projects))
where resources can be managed. Google Cloud offers a Free Tier and Free Trial
for multiple products. [Learn more
here](https://docs.cloud.google.com/free/docs/free-cloud-features).
## Clarifying Questions
Before proceeding, the agent should clarify the user's current status:
1. Do you already have a [Google Account](https://accounts.google.com/) (Gmail
or [Google Workspace](https://workspace.google.com/))?
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](https://console.cloud.google.com/)?
## Prerequisites
- A [Google Account](https://accounts.google.com/) (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](https://console.cloud.google.com/).
2. Sign in with your Google Account. This will "Activate" [your $300 free
credit](https://docs.cloud.google.com/free/docs/free-cloud-features#free-trial).
### 2. Create Your First Google Cloud Project
Google Cloud resources are organized into
**[Projects](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy#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](https://docs.cloud.google.com/billing/docs/how-to/manage-billing-account)
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](https://docs.cloud.google.com/sdk/docs/install-sdk)**
(`gcloud` CLI) is the primary tool for interacting with Google Cloud from your
local machine.
1. [Download and install the Google Cloud
CLI](https://cloud.google.com/sdk/docs/install).
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](https://docs.cloud.google.com/apis/docs/overview) to be enabled before
use. For example, to use [Cloud
Run](https://docs.cloud.google.com/run/docs/overview/what-is-cloud-run), run:
`gcloud services enable run.googleapis.com`
Note that [some Google Cloud APIs, including Cloud Logging, are enabled by
default](https://docs.cloud.google.com/service-usage/docs/enabled-service#default).
### 6. Deploy Your First Resource
Choose a simple entry point based on your needs:
- **[Cloud Run](https://docs.cloud.google.com/run/docs) (Recommended for Apps):**
Deploy a containerized "Hello World" app.
- **[Compute Engine](https://docs.cloud.google.com/compute/docs):** Create a
small Linux VM (e.g., `e2-micro` which is part of the Always Free tier in
certain regions).
- **[Cloud Storage](https://docs.cloud.google.com/storage/docs):** Create a
bucket to store files.
Example (Cloud Run):
```bash
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
- Explore the [Google Cloud Free Program](https://cloud.google.com/free) to
see what else you can do with your free credit.
- Read the [Google Cloud Overview](https://cloud.google.com/docs/overview)
- See the [full list of 150+ Google Cloud products](https://cloud.google.com/products)
- Explore the [Enterprise Setup Guide](https://docs.cloud.google.com/docs/enterprise/cloud-setup)
for information on setting up Google Cloud for a team or organization.
- Compare [AWS and Azure products to Google Cloud](https://docs.cloud.google.com/docs/get-started/aws-azure-gcp-service-comparison)
## Reference Directory
- [Google Cloud Setup Guide](reference/google-cloud-setup.md): Detailed
setup instructions and reference for Google Cloud onboarding.
## 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?
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.