メニュー
Guidance for using, changing, testing, and troubleshooting the Google Cloud CLI shim in this repository, including configuration mounts, kubeconfig mounting, and CLOUDSDK_* environment variable forwarding.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use and maintain the context-first Skopeo Shimmy tool.
Create or extend a Shimmy tool kind and its concrete CLI versions. Use when adding a wrapped CLI, selecting its image strategy, adding a version track, or wiring tool-local metadata, runtime, tests, guide, and agent guidance.
Install, update, validate, activate, or remove Shimmy profiles. Use for Shimmy lifecycle work outside the source checkout, profile selection, disposable-install validation, or manifest-based state inspection.
Use and maintain the context-first OpenShift CLI Shimmy tool.
Use and maintain the context-first OpenShift CLI Shimmy tool.
Create or extend a Shimmy tool kind and its concrete CLI versions. Use when adding a wrapped CLI, selecting its image strategy, adding a version track, or wiring tool-local metadata, runtime, tests, guide, and agent guidance.
| name | shimmy-tool-gcloud |
| description | Guidance for using, changing, testing, and troubleshooting the Google Cloud CLI shim in this repository, including configuration mounts, kubeconfig mounting, and CLOUDSDK_* environment variable forwarding. |
Use this skill when working with shims/gcloud, its tests, its docs, or gcloud usage through Shimmy.
../../../shims/gcloud../../../docs/shims/gcloud.md../../../scripts/test-shimmy.sh../../../scripts/install-shimmy.sh../../../README.md../../../CONTRIBUTING.md../../../docs/prompt-shimmy-project.mdWhen this skill is installed outside the Shimmy source checkout, do not rely on the repo-relative Files paths above. Prefer activated commands such as <tool> --version, inspect selected profile state with shimmy status --format manifest, and use SHIMMY_PROFILE_ACTIVE=upstream <tool> --version when validating the upstream profile. Use repo-local paths such as ./shims/<tool> only when intentionally editing or testing source files in the Shimmy checkout.
gcr.io/google.com/cloudsdktool/google-cloud-cli:stableSHIMMY_GCLOUD_IMAGESHIMMY_GCLOUD_IMAGE_PULL=alwaysCLOUDSDK_CONFIG--shimmy-config-help prints host HOME, host CLOUDSDK_CONFIG, expected gcloud/kubeconfig paths, effective config path, path presence, and mount policy before Podman preflightcloudsdkHOME=/home/cloudsdk, CLOUDSDK_CONFIG=/home/cloudsdk/.config/gcloud$PWD to /workCLOUDSDK_CONFIG, otherwise $HOME/.config/gcloud, to /home/cloudsdk/.config/gcloud:rw; the host directory is created during normal gcloud execution$HOME/.kube/config to /home/cloudsdk/.kube/config:ro when presentCLOUDSDK_*linux/amd64 on Linux and linux/arm64 on macOS--shimmy-config-help non-mutating; normal gcloud execution creates host CLOUDSDK_CONFIG when set, otherwise ~/.config/gcloud when HOME is set.cloudsdk with CLOUDSDK_CONFIG=/home/cloudsdk/.config/gcloud unless a future image removes that user or changes its home.:stable tag is the preferred default because Google documents it as supporting both linux/amd64 and linux/arm64.CLOUDSDK_* forwarding as the current contract; update docs and tests deliberately if it changes. Host CLOUDSDK_CONFIG should select the host mount source, and Shimmy's explicit container CLOUDSDK_CONFIG value should point to that mounted directory.gcloud info, gcloud version, and gcloud auth list for validation and information gathering.gcloud apply or gcloud destroy style operations unless the user explicitly asks for that operation and understands the consequences.shimmy-escalation workflow before using a non-shim fallback../shims/gcloud --shimmy-config-help./shims/gcloud --versiongcloud auth list (when authenticated)gcloud projects list (when authenticated)../shimmy-create-tool/SKILL.md under Learning Guidance.