From prega-release-notes
OpenShift Client Download — select, verify, and install official CLI binaries (OpenShift oc/kubectl/openshift-install, ROSA, Helm, opm, operator-sdk, and common helpers) from user-described needs on Linux or macOS, using mirror and vendor sites with checksum verification when available. Use when installing or upgrading oc, opm, kubectl, or related CLIs for prega-release-notes or other OpenShift workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prega-release-notes:openshift-client-downloadThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Upstream reference: [ai-helpers@b0e2950](https://github.com/midu16/ai-helpers/commit/b0e29501edb4722e6bdeae1ad67acab6a5483527) (`plugins/utils/skills/openshift-client-download`).
Upstream reference: ai-helpers@b0e2950 (plugins/utils/skills/openshift-client-download).
Use this skill when the user (or a slash command) asks to download, install, or pin versions of platform CLIs—especially OpenShift and cloud tooling—based on a natural-language description (for example: “oc and openshift-install for 4.16 on Linux arm64”, “latest stable ROSA CLI”, “helm 3 plus yq”).
x86_64 / amd64, aarch64 / arm64) and OS (Linux, macOS; Windows only if the user explicitly asks).PATH.curl or wget, tar/unzip as needed, sha256sum or shasum -a 256 for verification../.local/bin, $HOME/.local/bin, or a project-local ./bin).If something is missing, say what to install and offer a fallback (for example, package manager) only when the user wants it.
From the user’s description, extract:
X.Y.Z, “latest z-stream for 4.Y”, “stable channel”, or “latest GA”—if ambiguous, ask one short clarifying question before downloading large artifacts.uname -s and uname -m (or the user’s stated platform). Map aarch64 → arm64, x86_64 → amd64 where vendor filenames use the latter.Use these patterns; always re-resolve the exact URL from the vendor page or directory listing when the user cares about a specific patch, because paths change frequently.
oc, kubectl, and often openshift-install4.16.20/) for file names.openshift-client-linux-amd64-rhel9.tar.gz (or rhel8), often openshift-install-linux-*.tar.gz in the same version folder for IPI/UPI installers.openshift-client-linux-arm64-*.tar.gz.openshift-client-mac.tar.gz or openshift-client-mac-arm64.tar.gz.sha256sum.txt or SHA256SUM in the same directory as the tarball; verify before extracting.After extraction, common binaries: oc, kubectl; install may include openshift-install.
rosa)openshift/rosa when the user wants OSS bits—pick one source per session and stay consistent with checksums offered there.get.helm.sh/helm-vX.Y.Z-linux-amd64.tar.gz with published checksums.opm (Operator Package Manager)operator-sdkyq, jq, grpcurl: use upstream release pages and verify published checksums or vendor package signatures when available..work/openshift-client-download/<timestamp>/ in the repo, or a user-provided path outside git—never commit downloaded binaries).curl -fL --retry 3 -O <url> (or equivalent).tar/unzip into a staging/ subfolder, then copy only intended binaries into the install prefix.chmod +x on placed binaries.export PATH=..., and quick smoke tests (oc version --client, kubectl version --client, etc.).scripts/bootstrap_clients.py (Python; same mirror family as the prega 00_client_download.sh script). Merge that artifact list with this catalog when automating oc + opm for release notes—do not invent private URLs.Summarize the OpenShift Client Download run:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub midu16/prega-release-notes --plugin prega-release-notes