Google Cloud

What This Skill Does

The Google Cloud skill for OpenClaw empowers users to manage, monitor, and deploy infrastructure on GCP using battle-tested production patterns. It acts as an expert-level advisory and automation layer, helping developers avoid common pitfalls such as uncontrolled cost overruns, security misconfigurations, and networking bottlenecks. By integrating directly into your workflow, the skill provides actionable insights into IAM roles, VPC architecture, resource lifecycle management, and performance optimization strategies.

Installation

To integrate this skill into your environment, use the OpenClaw CLI or your dashboard to execute the following command: clawhub install openclaw/skills/skills/ivangdavila/gcp

Use Cases

• Cost Optimization Audits: Automatically analyze your current cloud footprint to identify "ghost" resources like unattached persistent disks, static IPs that aren't routed, or suboptimal egress patterns.
• Security Hardening: Provision new service accounts with strictly least-privilege roles, ensuring the default Compute Engine service account is not used for production workloads. It also assists in configuring Workload Identity Federation to replace insecure static keys with temporary tokens.
• Architecture Design: Receive expert guidance on choosing between regional or global load balancers, selecting the appropriate Cloud Functions generation (gen1 vs gen2), and designing database schema strategies to avoid Firestore hotspotting.
• Network Engineering: Configure VPCs and subnets with Private Google Access, ensuring your internal instances reach Google APIs without needing public IP addresses.

Example Prompts

• "Analyze my current GCP infrastructure and identify any idle resources or storage buckets that are racking up costs unnecessarily."
• "Help me configure a secure CI/CD pipeline using Workload Identity Federation for GitHub Actions to avoid storing service account keys."
• "What is the best way to handle high-traffic writes in Firestore to avoid document ID hotspotting? Provide a code example."

Tips & Limitations

• Always monitor costs: Remember that stopping a VM does not stop disk or static IP billing; always clean up these resources when instances are decommissioned.
• Understand limitations: The skill provides advice based on best practices, but always test infrastructure changes in a development environment before applying to production. Note that GKE Autopilot, while simplified, imposes strict limits on DaemonSets and privileged containers; ensure your application requirements align with these constraints before migrating.