Menú
Use and maintain the context-first OpenShift CLI Shimmy tool.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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.
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.
Request narrow AI-agent approvals for Shimmy wrappers that invoke Podman. Use when a wrapper is blocked by sandboxing or when Podman works directly but an exact outer wrapper command needs approval.
| name | shimmy-tool-oc |
| description | Use and maintain the context-first OpenShift CLI Shimmy tool. |
Read ../../../CONTEXT.md, ../CONTEXT.md, and the selected version context.
SHIMMY_OC_VERSION selects a supported local-build version; metadata defaults
to 4.20. Preserve publisher-supplied multi-architecture manifest-list digests
for default CLI images so the shared runtime helper can select the host platform.
Use oc --help for non-network smoke checks across supported versions.
Corporate registry mirrors for registry.redhat.io.
Registry mirrors must be configured in /etc/containers/registries.conf so
Podman pulls the oc image from the proxy registry instead of the upstream
Red Hat registry.
Mirror images and signatures together where possible. If the mirror does
not contain Red Hat signatures, a permissive policy.json entry is required
for the mirror host. A minimal example:
{
"default": [{ "type": "reject" }],
"transports": {
"docker": {
"your-mirror-host": [{ "type": "insecureAcceptAnything" }]
}
}
}
Be aware of Podman mirror fallback. If the mirror is misconfigured or missing blobs, Podman may fall back to the upstream registry, which can be blocked by strict signature policy.
Manually validate mirror pulls before relying on the shim. Use explicit
pulls such as podman --log-level=debug pull mirror-host/path/to/image@sha256:…
to confirm that the mirror is used and that blobs and signatures are present.
If oc image pulls fail from an Agent, inspect registry and policy errors. Check Podman logs for signature or policy failures and verify that the corporate mirror contains the required image digests and signatures.
Coordinate with registry administrators. Ensure that required oc images and signatures are mirrored for long-term secure use in proxy or airgapped environments.
The oc skill should surface mirror and signature-policy issues when image pulls
fail and offer actionable diagnostics (for example: suggest checking
registries.conf, testing a direct mirror pull with debug logging, and
reviewing policy.json for the mirror host).