shimmy-tool-oc

Select and maintain Shimmy OpenShift CLI versions for versioned oc workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you use and maintain the context-first OpenShift CLI tool wrapper for Shimmy, so you can select the correct oc version and work with local builds without manually searching the repository.

Core Features & Use Cases

  • Version-aware oc workflows: Select supported oc versions through SHIMMY_OC_VERSION and keep metadata aligned with the chosen release.
  • Local-image and runtime guidance: Follow the tool's instructions for host-platform selection, multi-architecture manifest handling, and non-network smoke checks.
  • Environment troubleshooting: Use the embedded guidance to diagnose corporate registry mirrors, signature-policy issues, and airgapped pull failures.
  • Use Case: If oc pulls fail in a restricted network, this Skill guides you to inspect registries.conf, policy.json, and mirror pull behavior before relying on the shim.

Quick Start

Ask for help using the OpenShift CLI skill for the currently selected Shimmy version and its mirror or signature-policy diagnostics.

Frequently Asked Questions about shimmy-tool-oc

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

FAQPage Schema
How do I select the correct oc version for OpenShift CLI workflows?

Select the correct oc version for OpenShift CLI workflows by setting the SHIMMY_OC_VERSION environment variable, which aligns tool metadata and execution behavior with your chosen release.

Why does my OpenShift CLI pull fail in a restricted or airgapped network?

OpenShift CLI pulls fail in restricted networks due to misconfigured corporate registry mirrors or signature policy issues, requiring you to inspect registries.conf and policy.json to diagnose the pull behavior.

How do I preserve manifest-list digests when running local OpenShift builds?

Preserve manifest-list digests during local OpenShift builds by following host-platform selection and multi-architecture manifest handling instructions, ensuring reliable non-network smoke checks without altering the digest.

Do I need to validate registry and signature policy configurations before using the OpenShift CLI?

You need to validate registry and signature policy configurations before using the OpenShift CLI to ensure reliable container runtime pulls, especially when operating within corporate mirror or airgapped environments.

What is the best way to troubleshoot corporate registry mirror issues with the oc command?

The best way to troubleshoot corporate registry mirror issues with the oc command is to use embedded diagnostic guidance to inspect mirror pull behavior, validate registries.conf, and verify signature policies.