compute

Provision and manage Google Compute Engine VM instances across zones and projects.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill compute-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compute
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/gcp/compute
Command: npx skills add https://github.com/theslashdojo/dojo --skill compute-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Provision and manage Google Compute Engine VMs for development, test, and production workloads, simplifying infrastructure provisioning and lifecycle management.

Core Features & Use Cases

  • Create, configure, and launch VM instances across zones
  • Attach disks, set boot options, and configure network/firewall rules
  • Start, stop, describe, and delete instances; manage SSH access and startup scripts

Quick Start

Create a VM named my-vm in the us-central1-a zone using Debian 12 with a basic machine type.

Frequently Asked Questions about compute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a Google Compute Engine VM and configure its boot options?

To provision a Google Compute Engine VM, you can create and configure instances across zones by specifying the machine type, boot image, and attached disks. This simplifies infrastructure provisioning by managing launch options directly.

What IAM roles do I need to manage GCE instances and configure firewall rules?

Managing GCE instances requires gcloud CLI access and IAM roles like compute.instanceAdmin.v1 or compute.admin. These permissions allow you to create instances, configure network firewall rules, and manage SSH access securely.

Can I manage SSH access and startup scripts for Compute Engine VMs?

Yes, you can manage SSH access and configure startup scripts for Compute Engine VMs. This allows you to automate instance initialization, execute commands upon boot, and securely handle virtual machine lifecycle operations.

How do I start, stop, and delete GCE instances across different zones and projects?

You can start, stop, describe, and delete GCE instances across different zones and projects using gcloud CLI commands. This lifecycle management ensures you can efficiently control development, test, and production workloads.

What is the best way to automate Google Compute Engine lifecycle management for production workloads?

Automating Google Compute Engine lifecycle management involves using scripts to provision, start, stop, and delete instances. This approach streamlines infrastructure provisioning for development, test, and production workloads without manual console intervention.

Does provisioning a GCE VM require gcloud CLI access for network and firewall configuration?

Yes, provisioning a GCE VM requires gcloud CLI access to configure network and firewall rules. This ensures secure instance deployment and proper network isolation across your specified zones and projects.