Create New Openclaw In Gcp

What This Skill Does

The 'Create New Openclaw In Gcp' skill automates the end-to-end provisioning of an OpenClaw AI agent node within the Google Cloud Platform (GCP) ecosystem. Developed by divide-by-0, this skill handles the heavy lifting of cloud infrastructure setup, including VM instantiation (e2-medium), SSH key configuration, network hardening via UFW, Tailscale integration for secure connectivity, and full OpenClaw software lifecycle management. By encapsulating these complex operations into a reproducible workflow, it ensures that your AI agent environment is consistently deployed with the necessary environmental variables, dependencies like Node.js via NVM, and secure API integration with Anthropic and Brave Search.

Installation

To integrate this skill into your environment, use the OpenClaw Hub command line interface. Execute the following command in your terminal:

clawhub install openclaw/skills/skills/divide-by-0/create-new-openclaw-in-gcp

Ensure that you have your GCP credentials exported as environment variables prior to installation to allow the agent to interface with your Google Cloud account without manual interruption.

Use Cases

This skill is ideal for developers and AI engineers who need to deploy multiple isolated OpenClaw instances for specific agentic tasks. It is particularly useful for building scalable bot swarms where each agent requires its own dedicated infrastructure. It also serves as a robust foundation for researchers requiring a standardized environment for testing agent behavior under different network conditions, leveraging Tailscale for secure, cross-node communication in private mesh networks.

Example Prompts

1. "OpenClaw, please deploy a new agent instance to my GCP us-central1-a project using the existing credentials."
2. "Can you set up a new OpenClaw node in GCP and configure it to use my Brave Search API key?"
3. "Run the provisioning script to spin up a new virtual machine and install the latest version of the OpenClaw daemon."

Tips & Limitations

When using this skill, always ensure your SSH keys are correctly generated and present in your local ~/.ssh directory before triggering the installation. Note that this skill requires administrative permissions on the target GCP project and makes persistent modifications to VM configuration files. For security, ensure the ANTHROPIC_TOKEN and BRAVE_API_KEY are kept strictly in your local environment variables and never hard-coded into your scripts or shared repositories. Be aware that this skill creates resources that may incur ongoing charges on your GCP billing account; monitor your VM usage to prevent unexpected costs.