Skip to content
TrustedSkillsbeta
Back to all skills

Gcloud

Listed
dicklesworthstone·vlatest·cloud

Gcloud enables you to manage Google Cloud resources via command-line, streamlining deployments and infrastructure operations.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill gcloud -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dicklesworthstone

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: sdk.cloud.google.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    sdk.cloud.google.comundeclared

    What it found

    • skills/gcloud/SKILL.md:18contacts sdk.cloud.google.com
      curl https://sdk.cloud.google.com | bash
  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • skills/gcloud/SKILL.md:18remote script piped into a shell
      curl https://sdk.cloud.google.com | bash
  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • Pinned to a commit: passed

    Scanned dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations at 4d332440c3.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 492 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The gcloud skill enables AI agents to interact directly with Google Cloud Platform via the command-line interface, executing infrastructure tasks and managing resources programmatically. It allows agents to deploy applications, configure networking, and monitor services without manual intervention.

When to use it

  • Automating routine DevOps tasks like instance provisioning or image updates.
  • Querying cloud resource status to trigger alerts or scaling events.
  • Deploying containerized applications to Google Kubernetes Engine (GKE).
  • Managing IAM permissions and service account keys dynamically.

Key capabilities

  • Execution of standard gcloud CLI commands within the agent's environment.
  • Direct interaction with Compute Engine, Cloud Storage, and Container Registry.
  • Handling authentication using existing credentials or service account files.
  • Parsing command output for structured data extraction.

Example prompts

  • "Deploy a new web instance to us-central1-a using the latest Docker image from our registry."
  • "List all active Compute Engine instances and their current status."
  • "Create a new Cloud Storage bucket named 'logs-archive' with public read access."

Tips & gotchas

Ensure your AI agent has valid authentication credentials (like a service account key) configured before attempting to execute commands. Be cautious when granting broad permissions, as the agent could inadvertently modify critical production resources if not properly constrained.