openshift release-tests
COMMUNITYLABSCO SUMMARY
openshift-expert is a general OpenShift-and-Kubernetes knowledge skill: cluster architecture, operators, networking, storage, troubleshooting, and CI/CD pipelines, aimed at analyzing test failures, debugging cluster issues, and investigating build problems. release-workflow is narrower and specific to this repository's own tooling: it covers the Errata Reliability Team's z-stream release orchestration — build promotion, test analysis, advisory workflows, and the Konflux/Errata pipeline — with task sequencing and checkpoints pinned to OpenShift releases 4.12 through 4.20.
The repository around these two skills is ERT, a Python CLI (OAR) plus a Prow job controller that automates Errata, Jira, Google Docs, Slack, and Jenkins for the team that manages OpenShift's periodic z-stream releases. The skills exist to give an agent that same domain knowledge, not to replace the CLI itself. Outside that specific release process — including most other OpenShift or Kubernetes users — neither skill has much to offer.
READ THE FULL ANALYSIS
What it costs to start. Our data labels openshift-expert as needing an account/key and release-workflow as needing an MCP service; neither is usable with nothing configured. The README itself never mentions an agent-skills install path at all — it documents pip3 install -e . for the OAR and job-controller tooling, and says nothing about how the two skills are packaged or installed on top of it.
Pinned to a version range. release-workflow's own description scopes itself to releases 4.12–4.20; nothing in what we captured says whether it is kept current as OpenShift ships newer z-streams past that range.
WHAT'S INSIDE
2 showing · 2 totalopenshift-expert
A veteran OpenShift engineer on call: hand it a broken cluster or a failed test run, and it works out what went wrong, whether the blame lies with the product, a flaky test or the infrastructure, and what to do next.
release-workflow
Shepherds a new OpenShift version through every check and sign-off it needs before it can ship, and remembers how far it got, so a release picked up days later carries on from exactly where it stopped.
HOW TO GET IT
npx skills add openshift/release-testsnpx skills add openshift/release-tests --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.