shimmy-tool-gcloud

Maintain Google Cloud CLI shim workflows with config, kubeconfig, and environment forwarding.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-gcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shimmy-tool-gcloud
Source: https://github.com/wadebee/shimmy/tree/main/tools/gcloud/agent
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-gcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you use and maintain the Google Cloud CLI in Shimmy while preserving the expected config, kubeconfig, and environment forwarding behavior.

Core Features & Use Cases

  • Context-aware maintenance: Follows the repository's context-first structure so changes stay aligned with the canonical tool guidance.
  • Cloud SDK workflow support: Maintains Google Cloud CLI behavior, including configuration and kubeconfig mount rules.
  • Version-specific guidance: Works with the targeted tool version context so you can update, diagnose, or extend the gcloud shim confidently.

Quick Start

Use this skill to inspect the Google Cloud CLI Shimmy instructions and follow the linked repository context before making any changes.

Frequently Asked Questions about shimmy-tool-gcloud

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

FAQPage Schema
How do I preserve kubeconfig and environment variables when running gcloud commands?

To preserve kubeconfig and environment variables when running gcloud commands, use a context-aware CLI shim that maintains configuration forwarding behavior. This approach follows canonical repository context rules to ensure environment settings persist across command executions.

What is the best way to maintain Google Cloud CLI configuration context across repository changes?

Maintaining Google Cloud CLI configuration context requires following a context-first repository structure. By adhering to canonical tool guidance and Cloud SDK mount rules, configuration changes stay aligned with version-specific gcloud shim behavior.

How does a gcloud shim workflow handle Cloud SDK mount rules?

A gcloud shim workflow handles Cloud SDK mount rules by applying context-first repository changes that preserve configuration and kubeconfig forwarding. This ensures the Google Cloud CLI maintains expected behavior across targeted tool versions.

Can I use this gcloud CLI maintenance approach for version-specific Cloud SDK updates?

Yes, you can use this gcloud CLI maintenance approach for version-specific Cloud SDK updates. It works with targeted tool version context, allowing you to update, diagnose, or extend the gcloud shim configuration confidently.

Why does my Google Cloud CLI lose configuration context after running shimmed commands?

Your Google Cloud CLI loses configuration context when shim workflows fail to preserve environment forwarding behavior. Applying canonical repository context and Cloud SDK mount rules ensures kubeconfig and configuration settings persist correctly.