compute-vm-creation
Guides the planning, configuration, and provisioning of standalone Google Compute Engine virtual machines (VMs) and bare metal (-metal) instances using gcloud CLI commands or direct MCP tool execution.
Install / Use
npx skills add google/skills --skill compute-vm-creationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of compute-vm-creation
compute-vm-creation scores 91/100 on our quality scale, 444th of 1,108 Security skills we index (top 41%).
Its SKILL.md is 32 KB long, well organised into 14 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 20,340 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so compute-vm-creation is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
compute-vm-creation compared with similar skills
All 4 of these similar skills score higher than compute-vm-creation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| compute-vm-creation (this skill)by google | 91 | 20.3k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install compute-vm-creation?
- Run
npx skills add google/skills --skill compute-vm-creation. The install tabs above show the steps for each supported agent. - Which AI agents does compute-vm-creation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is compute-vm-creation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is compute-vm-creation still maintained?
- The repository was last updated about 2 months ago, so compute-vm-creation is actively maintained.
Skill content
View source on GitHubname: compute-vm-creation description: >- Guides the planning, configuration, and provisioning of standalone Google Compute Engine virtual machines (VMs) and bare metal (-metal) instances using gcloud CLI commands or direct MCP tool execution. Use ONLY when the user wants to create, configure, or provision a new standalone Compute Engine VM or bare metal instance from conversational intents (hardware sizing, region selection, OS image, networking, security defaults). DO NOT read or use for Google Kubernetes Engine (GKE) Autopilot or Standard clusters, Kubernetes node pools or Pods, container orchestration, managing existing VMs, Managed Instance Groups (MIGs), or Instance Templates. metadata: version: "1.0.0" category: Compute
Compute Engine VM Creation
This skill provides an interactive, intent-based experience for provisioning
standalone Google Compute Engine VM and bare metal (-metal) instances. It
supports users ranging from beginners asking to "create a VM" to cloud engineers
requiring customized infrastructure, mapping natural language intents to secure
Compute Engine configurations grounded in the Golden Path.
MCP Tools:
list_instances,create_instance,get_instance_basic_info,delete_instance,get_zone_operation,list_machine_types,list_accelerator_types,list_images
Usage Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read and follow the instructions in
Usage Attribution. Never include attribution
environment variables or User-Agent tags in generated scripts, Terraform, or
copy-pasteable commands shown to the user.
Prerequisites
Ensure the following setup requirements are met before provisioning instances.
Any host modifications (such as installing or updating the gcloud CLI,
installing or configuring the Google Compute Engine MCP server, or modifying
local environment configuration) must be explicitly approved by the user before
execution.
- Cloud SDK Installation: Verify
gcloudis installed (gcloud --version, Google Cloud SDK >= 480.0.0) only when executing live CLI commands. If missing or outdated, ask the user for explicit approval before installing or updating via Install the gcloud CLI. - Compute Engine MCP Server: For direct MCP tool execution
(
list_instances,create_instance,get_instance_basic_info,delete_instance,get_zone_operation,list_machine_types,list_accelerator_types,list_images), check whether the Compute Engine MCP tools are loaded in your active tool declarations, or ask the user for approval to configure the server following Use the Compute Engine MCP server. - Billing Account: Confirm the target Google Cloud project has an active billing account linked (required even when using Google Cloud Free Tier resources).
- Authentication: Authenticate your environment for CLI execution
(
gcloud auth login), application/MCP SDKs (gcloud auth application-default login), or service account credentials (GOOGLE_APPLICATION_CREDENTIALS). - Project Selection & API Enablement: Set the target project and enable the
Compute Engine API:
gcloud config set project {project_id} gcloud services enable compute.googleapis.com - Required IAM Roles:
- Caller Roles:
roles/compute.instanceAdmin.v1(to create and manage instances),roles/iam.serviceAccountUser(to attach{custom_service_account}), androles/mcp.toolUserwhen invoking the Compute Engine MCP server. - IAP SSH/RDP Access for Private (
--no-address) VMs: Connecting viagcloud compute ssh {vm_name} --zone={zone} --tunnel-through-iaprequiresroles/iap.tunnelResourceAccessorplus a VPC firewall rule allowing TCP22(or3389for RDP) from IAP's forwarding range35.235.240.0/20(see Use IAP for TCP forwarding). - Custom VM Service Account Setup: Fresh projects only contain the default
Compute Engine service account. If
{custom_service_account}does not yet exist, create a dedicated least-privilege service account first (seeking user approval before granting IAM bindings):gcloud iam service-accounts create {sa_name} \ --project={project_id} \ --display-name="{sa_display_name}" gcloud projects add-iam-policy-binding {project_id} \ --member="serviceAccount:{sa_name}@{project_id}.iam.gserviceaccount.com" \ --role="roles/logging.logWriter" gcloud projects add-iam-policy-binding {project_id} \ --member="serviceAccount:{sa_name}@{project_id}.iam.gserviceaccount.com" \ --role="roles/monitoring.metricWriter"
- Caller Roles:
Workflow
- Determine Execution Method & MCP Capability Boundary:
- Fast Conversational Intake (No Shell Probing on Missing Inputs): When a
user asks to configure or create a VM without providing mandatory inputs
(
project_id,vm_name,region/zone, or public vs. private networking), respond immediately after readingSKILL.mdwithout runninggcloud config list,gcloud --version, or any shell commands. Clarify that you can either execute provisioning once confirmed (Automated Execution) or provide copy-pasteablegcloudcommands / JSON payloads (Manual Execution), recommend a sizing tier, and ask for the missing inputs in a single turn. - MCP vs.
gcloudRouting Rule: Compute Engine MCP discovery tools (list_instances,get_instance_basic_info,list_machine_types,list_accelerator_types,list_images,get_zone_operation) are ideal for read-only inspection. However, MCPcreate_instance(McpCreateInstanceRequest) accepts only eight flat top-level fields (project,zone,name, baremachineType,imageProject,imageFamily,guestAccelerators,maintenancePolicy) and hardcodesglobal/networks/defaultwithout--no-address, custom subnets, custom service accounts, Shielded VM flags, OS Login, Spot scheduling, or custom disk sizes/types. Route all hardened (--no-address, custom--subnet={subnet},{custom_service_account}, Shielded VM, OS Login), Spot, custom-disk, 4th-gen Hyperdisk, and bare metal (-metal) creations togcloud compute instances create(or RESTinstances.insert) rather than dropping security guardrails to fitcreate_instance. Use MCPcreate_instanceonly for default-VPC prototyping when default disk and service-account settings are explicitly acceptable.
- Fast Conversational Intake (No Shell Probing on Missing Inputs): When a
user asks to configure or create a VM without providing mandatory inputs
(
- Gather Mandatory Inputs: ALWAYS ask the user for any missing inputs:
- Project ID (Ask directly if not provided in the prompt).
- VM Name (Offer a friendly default suggestion if unsure, e.g.,
my-first-web-server). - Region & Zone (Explain why simply: "Choosing a location closer to
you or your users reduces latency and makes things load faster." Recommend
us-central1/us-central1-aif the user has no preference, and consult Regions and zones, GPU regions and zones, or Google Cloud locations only when verifying non-default regional availability):gcloud config set compute/region {region} gcloud config set compute/zone {zone}
- Conversational Triage (Sizing, Generation & OS): Map the user's workload
to the Intent-Based Sizing Tiers and hardware generation defaults:
- Default OS images: Use
debian-12(debian-cloud) forE2,N2,C3virtualized, andC2D; usedebian-13(debian-cloud) for 4th-gen (C4,N4,X4) and bare metal (c3-standard-192-metal,c4-standard-288-metal, wheredebian-12is unsupported); usedebian-12-arm64/debian-13-arm64for ArmC4A; and usecommon-cu129-ubuntu-2404-nvidia-580(deeplearning-platform-release) forG2GPUs. Consult Operating system details and Bare metal instances only when selecting non-default OS images or bare metal SKUs. - Storage by generation: Use
hyperdisk-balancedon 4th-gen (C4,N4,C4A,C4D,M4,X4,A4) and bare metal (-metal) instances wherepd-*disks are rejected (N4supportshyperdisk-balancedandhyperdisk-throughput, nothyperdisk-extreme;H3supportspd-balancedandhyperdisk-balanced). Consult the "Machine series support for Hyperdisk" section of About Google Cloud Hyperdisk only for non-default disk types.
- Default OS images: Use
- Determine Network Accessibility & Subnet: ALWAYS ask in plain,
non-technical language whether the VM needs to be reachable from the public
internet or kept private, noting that private networking (
--no-address) is the security best practice—even when hosting a website or web app. Use--subnet={subnet}(verifying whether a custom/Shared VPC subnet ordefaultVPC exists, since many enterprise projects enforceconstraints/compute.skipDefaultNetworkCreation). - Configure Security, OS Login & Service Accounts: Enable IAM-governed SSH
via
--metadata=enable-oslogin=TRUE, recommend a custom least-privilege service account ({custom_service_account}), and enable Shielded VM flags (--shielded-secure-boot,--shielded-vtpm,--shielded-integrity-monitoring) on virtualized VMs (on standard x86-metalbare metal instances, pass--no-shielded-secure-bootand omit vTPM/integrity flags). - Summarize & Confirm (Mode-Aware): Present a clear summary of the proposed
VM configuration, cost profile, and architectural warnings:
- Automated Execution Mode: Always ask for explicit user confirmation before executing any mutating provisioning command or tool call (e.g., "Would you like me to proceed with provisioning this configuration, or adjust any settings first?").
- Manual /
"Do not execute"Mode: Instruct the user to review and substitute any{snake_case}placeholders (such as{subnet}or{custom_service_account}) before running the command in their terminal; do not offer to execute provisioning when tools are disconnected or execution was forbidden.
- Execute or Deliver Payloads:
- Automated: Execute
gcloud compute instances create(prefixed withCLOUDSDK_METRICS_REQUEST_ATTRIBUTIONper Usage Attribution) for hardened/Spot/4th-gen/ bare-metal configurations, or call MCPcreate_instancefor default-VPC prototyping, tracking progress viaget_zone_operationand verifying viaget_instance_basic_info. - Manual: Output formatted, copy-pasteable
gcloudCLI commands (without--quietor attribution prefixes) or JSON payloads with clear instructions.
- Automated: Execute
- Verify, Deliver Next Steps & Teardown Guidance: Provide post-provisioning
access steps (for example, via
--tunnel-through-iapwithgcloud compute ssh) and always include teardown instructions (omitting--quietso interactive confirmation prevents accidental data loss; see [Delete a VM](https://docs.cloud.google.com/compute/docs/instances/de
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
