New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Cloud Build Basics

by google in google/skills

Teaches the fundamentals of Google Cloud Build (GCB). An agent skill from google/skills.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Cloud Build Basics

skills CLI
$ npx skills add google/skills --skill cloud-build-basics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install google/skills cloud-build-basics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cloud/cloud-build-basics .claude/skills/cloud-build-basics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cloud-build-basics
GitHub stars
21k
Token cost
~2k tokens
SKILL.md length
918 words
Files
4 (incl. references)
Skills in repo
145
Repo updated
First seen
Licence
Apache-2.0

At a glance

Teaches the fundamentals of Google Cloud Build (GCB). An agent skill from google/skills.

  • Works in 4 steps: Start Trigger Creation → Configure Trigger Settings → Configure Build Settings → …
  • Managing private pools
  • SKILL.md covers Prerequisites, Core Concepts, Navigation: Viewing Build… and Creating a Basic Automated…, plus 3 more sections
  • Calls gcloud; reaches console.cloud.google.com

What it does

Cloud Build Basics is an agent skill from google/skills, published by the product's own GitHub organization. Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/cb-create-trigger.md`, `references/cb-list-build-zero-state.md` and `references/cb-run-trigger.md`).

It sits in DevOps & Cloud. It works with Google Cloud and Docker. The repository describes itself as: Agent Skills for Google products and technologies. The licence is Apache-2.0.

When your agent uses it

  • Managing private pools
  • Complex pipeline architectures

Example prompts

  • “Use the cloud-build-basics skill to teach the fundamentals of Google Cloud Build (GCB). An agent skill from google/skills”
  • “/cloud-build-basics”

Requirements

  • Docker

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Start Trigger Creation
  2. Configure Trigger Settings
  3. Configure Build Settings
  4. Save and Test

What it can do on your machine

Read from SKILL.md and the folder at commit 8a1ac05. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gcloud

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • console.cloud.google.com

    Also links to:

    • cloud.google.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cloud Build Basics loads about 2k tokens when it runs, and up to ~8.4k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 918 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from google/skills at commit 8a1ac05, republished under its Apache-2.0 licence (© google). 918 words, ~2,045 tokens.

Download SKILL.mdSave it as .claude/skills/cloud-build-basics/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
cloud-build-basics
description
Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
metadata.version
1.0.0
metadata.category
DevOps

Google Cloud Build Basics

Prerequisites

Before starting, ensure the following prerequisites are met:

  1. Google Cloud SDK: Ensure the Google Cloud SDK is installed and configured.
  2. Authentication: Authenticate the gcloud CLI:
    bash
    gcloud auth login
gcloud auth application-default login
  3. Project ID: Know the target Google Cloud Project ID. Set the context:
    bash
    gcloud config set project <PROJECT_ID>
  4. Enable Cloud Build API: The Cloud Build API must be enabled for the project.
    bash
    gcloud services enable cloudbuild.googleapis.com
  5. Permissions: Ensure the user or service account has the necessary permissions, such as roles/cloudbuild.builds.editor and roles/serviceusage.serviceUsageAdmin (to enable the API).

Core Concepts

Google Cloud Build (GCB) is a serverless platform that executes your builds on Google Cloud. It translates your source code into deployable artifacts, such as Docker containers or Java archives.

ConceptDescription
cloudbuild.yamlThe required configuration file that defines the build steps. It is written in YAML or JSON.
Build StepsA sequence of actions (steps) GCB performs. Each step runs a command inside a specific Docker container (the builder). Common builders include gcr.io/cloud-builders/gcloud, gcr.io/cloud-builders/docker, and custom containers.
ArtifactsThe output of the build, typically a container image pushed to Google Container Registry (GCR) or Artifact Registry (AR), or other deployable files.
TriggersAutomation rules that invoke a build in response to an event, such as a push to a Git repository, a Pub/Sub message, or a manual request.

Navigation: Viewing Build History

The Cloud Build Build History page is the central place to monitor the status of past and ongoing builds.

  1. Open the Cloud Console: Navigate to the Google Cloud Console.
  2. Go to Cloud Build: Use the search bar or the navigation menu to find Cloud Build.
  3. Select Build History: In the left navigation pane, select History (or use the direct URL: https://console.cloud.google.com/cloud-build/builds).
  4. Review Builds:
    • Status: Check the status column (SUCCESS, FAILURE, WORKING, QUEUED).
    • Region: Use the region filter at the top to view builds that ran in a specific region (important for regional worker pools).
    • Logs: Click on a specific Build ID to view the detailed logs, execution steps, and build summary. This is crucial for debugging failed builds.

[!NOTE] If this is your first time visiting the page, you might see the "zero-state" experience, which offers options to run a sample build or create your first trigger (as noted in the cb-list-build-zero-state skill). Note that region settings for triggers and builds are immutable after creation and must be chosen deliberately.

Creating a Basic Automated Trigger

This process defines an automation rule to run a build whenever code is pushed to a specified Git branch.

Step 1: Start Trigger Creation
  1. Navigate to the Cloud Build Triggers page (https://console.cloud.google.com/cloud-build/triggers).
  2. Click Create trigger.
Step 2: Configure Trigger Settings
  1. Name: Provide a unique, descriptive name (e.g., github-main-branch-build).
  2. Region: Select the region where the trigger configuration will be stored (e.g., global or a specific regional endpoint). Note: Trigger and build region settings are immutable after creation and must be chosen deliberately.
  3. Event: Select the event type. For automated CI/CD, select Push to a branch.
  4. Source: Select the repository source:
    • Repository: Connect your source repository (GitHub, Bitbucket, Cloud Source Repositories, etc.). If needed, authorize the connection.
    • Repository Name: Select the specific repository you want to link.
  5. Branch: Enter the branch pattern (e.g., ^main$ or ^develop).
Show full SKILL.md (363 more words)Show less
Step 3: Configure Build Settings
  1. Configuration: Select Cloud Build configuration file (yaml or json).
  2. Location: Keep the default Repository and specify the path to your build configuration file (e.g., cloudbuild.yaml).
    • Alternative: For very simple builds, you can choose Inline to paste the YAML configuration directly into the trigger.
  3. (Optional) Service Account: For production environments, select a dedicated service account with limited permissions to enforce the principle of least privilege.
Step 4: Save and Test
  1. Click Create. The trigger is now active and will run automatically on the next matching Git push.

[!TIP] The cb-create-trigger skill provides detailed gcloud commands for creating triggers across all types (GitHub, Pub/Sub, Webhook) and configurations (inline, Dockerfile, YAML). Use that skill for CLI automation.

Running an Existing Trigger Manually

Sometimes you need to run a trigger on demand, outside of its normal automation flow (e.g., to rebuild an old commit or test a new substitution).

[!IMPORTANT] Substitution Immutability: You can only override values for substitution variables that are already defined in the trigger configuration. You cannot introduce new substitution variable keys at runtime.

Option A: Via the Cloud Console
  1. Navigate to the Cloud Build Triggers page (https://console.cloud.google.com/cloud-build/triggers).
  2. Locate the trigger you wish to run.
  3. Click the vertical ellipsis (⋮) next to the trigger and select Run.
  4. A dialog will appear, allowing you to specify:
    • Source branch/tag: Choose the specific Git reference to build from.
    • Substitution Variables: Override any existing substitution variables (e.g., set _VERSION to a new value).
  5. Click Run trigger. The build will start immediately, and you can monitor its status on the History page.
Option B: Via the gcloud CLI

Use the gcloud builds triggers run command to invoke the trigger and optionally override parameters.

bash
# Run the trigger against the 'main' branch
gcloud builds triggers run <TRIGGER_NAME> \
    --region=<REGION> \
    --branch=main

# Run the trigger and override a substitution variable
gcloud builds triggers run <TRIGGER_NAME> \
    --region=<REGION> \
    --branch=main \
    --substitutions=_IMAGE_TAG="20231027-manual"

# Monitor the initiated build
# Note: The run command outputs the build ID. Use it to check status:
# gcloud builds log <BUILD_ID> --region=<REGION>

[!NOTE] The cb-run-trigger skill provides more complex invocation examples, including running against a specific commit SHA or using tags.

  • cb-create-trigger: Detailed CLI-focused instructions for creating all trigger types.
  • cb-list-build-zero-state: Advanced management of the Cloud Build dashboard and onboarding zero state.
  • cb-run-trigger: Comprehensive guide to manually running triggers using various gcloud options.

External Resources & Documentation

© google, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/cloud/cloud-build-basics of google/skills.

  • SKILL.md
  • references/cb-create-trigger.md
  • references/cb-list-build-zero-state.md
  • references/cb-run-trigger.md

Open the folder on GitHubat commit 8a1ac05

Compare with similar skills

Cloud Build Basics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cloud Build Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cloud Build Basics this skillgoogle/skills21k—~2kAutomated safety check: PassApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2596 repos~1.1kAutomated safety check: NotesCustom licence
Devopsnicepkg/auto-company1922 repos~814Automated safety check: PassMIT
Pi K8s Deployrodrigorodrigues/microservices-design-patterns188—~1.6kAutomated safety check: PassNone
Logfire Infrastructurepydantic/skills140—~1.8kAutomated safety check: PassMIT
DeployingGoogleCloudPlatform/race-condition234—~3kAutomated safety check: PassCustom licence

Similar skills

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    259 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • Devops

    nicepkg/auto-company

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm).

    192 GitHub starsUsed in 2 repos~814 tokens
    DevOps & CloudAuto-check passed

  • Pi K8s Deploy

    rodrigorodrigues/microservices-design-patterns

    Check Docker Hub for a new :latest image on a managed service and roll it out to the home Pi k8s cluster, the same way authentication-service was deployed on 2026-08-29 (SSH + kubectl rollout…

    188 GitHub stars~1.6k tokensUpdated 19 days ago
    DevOps & CloudAuto-check passed

  • Logfire Infrastructure

    pydantic/skills

    Official

    Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.

    140 GitHub stars~1.8k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed

  • Deploying

    GoogleCloudPlatform/race-condition

    Guides deployment of Race Condition to a GCP project. An agent skill from GoogleCloudPlatform/race-condition.

    234 GitHub stars~3k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Performing Cloud Asset Inventory With Cartography

    mukul975/Anthropic-Cybersecurity-Skills

    Run Cartography to sync AWS, GCP, or Azure resources into a Neo4j graph database, mapping relationships such as IAM permission chains, network paths, and cross-account trust.

    34k GitHub stars~1.7k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from google/skills

All 145 skills in this repo

  • Google Cloud PAM Helper

    google/skills

    Official

    Manages Google Cloud Privileged Access Manager entitlements and grants: create and edit entitlements, request temporary access, and approve or deny pending grants.

    21k GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • Agent Platform Alert Configuration

    google/skills

    Official

    Writes Terraform alerting policies for AI agents that emit OpenTelemetry metrics, covering reliability, cost, safety, security and quality signals on Google Cloud.

    21k GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed

  • Model Garden Deployment

    google/skills

    Official

    Deploys open models or custom weights from Model Garden to Agent Platform endpoints, checks deployment status and cleans up endpoints, confirming before any change.

    21k GitHub stars~5.1k tokensUpdated yesterday
    Auto-check passed

  • Agent Platform Skill Registry

    google/skills

    Official

    Searches, manages and scaffolds skills in the Gemini Enterprise Agent Platform Skill Registry using bundled Python scripts and Google Cloud credentials.

    21k GitHub stars~584 tokensUpdated yesterday
    Auto-check passed

  • GCP Application Design Center Deploy

    google/skills

    Official

    Designs GCP infrastructure as local Terraform, validates and scans it against best practices, then imports it to Application Design Center for deployment and troubleshooting.

    21k GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed

  • BigQuery Slot and Cost Optimizer

    google/skills

    Official

    Analyzes BigQuery slot use, query costs and execution bottlenecks from INFORMATION_SCHEMA to diagnose slow queries, slot contention and unpartitioned scans.

    21k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Cloud Build Basics

What does Cloud Build Basics do?

Teaches the fundamentals of Google Cloud Build (GCB). An agent skill from google/skills. Cloud Build Basics is an agent skill from google/skills, published by the product's own GitHub organization. Teaches the fundamentals of Google Cloud Build (GCB).

When should I use Cloud Build Basics?

Cloud Build Basics fits situations like: managing private pools; complex pipeline architectures.

How do I install Cloud Build Basics in Claude Code?

Run `npx skills add google/skills --skill cloud-build-basics -a claude-code`. Or copy the skill folder (skills/cloud/cloud-build-basics in google/skills) into .claude/skills/cloud-build-basics in your project. Claude Code loads it when a task matches its description.

How do I install Cloud Build Basics in Codex?

Run `npx skills add google/skills --skill cloud-build-basics -a codex`. Or copy the skill folder (skills/cloud/cloud-build-basics in google/skills) into .agents/skills/cloud-build-basics in your project. Codex loads it when a task matches its description.

Can I use Cloud Build Basics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add google/skills --skill cloud-build-basics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloud-build-basics, .gemini/skills/cloud-build-basics, .github/skills/cloud-build-basics and .opencode/skills/cloud-build-basics in your project.

What does Cloud Build Basics need to run?

Going by SKILL.md and its folder, Cloud Build Basics needs the command-line tools its instructions call (gcloud). Our summary lists: Docker.

Does Cloud Build Basics access the network?

SKILL.md names 2 domains. In commands or code: console.cloud.google.com; the agent is likely to contact it when it follows the instructions. As links in the text: cloud.google.com. This is read from the text; nothing was executed.

Is Cloud Build Basics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cloud Build Basics use?

Cloud Build Basics is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cloud Build Basics use?

About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.3k tokens, read only when the agent opens those files.

What are the alternatives to Cloud Build Basics?

Skills that share tags, products or a category with Cloud Build Basics: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars), Devops (nicepkg/auto-company, 192 stars), Pi K8s Deploy (rodrigorodrigues/microservices-design-patterns, 188 stars) and Logfire Infrastructure (pydantic/skills, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cloud Build Basics?

google (a GitHub organization, an official publisher) maintains it in google/skills, which has 20,994 GitHub stars. The repository holds 145 skills in this directory. The repository was last updated on October 6, 2026.

Source: google/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.