Deploy Observability
aliyun/alibabacloud-observability-mcp-server
Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).
Analyze Go builder images, declared Go versions, or Go module versions across an OpenShift release using the golang plugin's release inventory scripts.
Install Analyze Release Go Versions
$ npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers analyze-release-go-versions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/golang/skills/analyze-release-go-versions .claude/skills/analyze-release-go-versions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyze-release-go-versions" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versions into .claude/skills/analyze-release-go-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-release-go-versions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers analyze-release-go-versions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/golang/skills/analyze-release-go-versions .agents/skills/analyze-release-go-versions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-release-go-versions" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versions into .agents/skills/analyze-release-go-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-release-go-versions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers analyze-release-go-versions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/golang/skills/analyze-release-go-versions .cursor/skills/analyze-release-go-versions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyze-release-go-versions" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versions into .cursor/skills/analyze-release-go-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-release-go-versions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/golang/skills/analyze-release-go-versions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers analyze-release-go-versions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/golang/skills/analyze-release-go-versions .gemini/skills/analyze-release-go-versions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyze-release-go-versions" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versions into .gemini/skills/analyze-release-go-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-release-go-versions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-eng/ai-helpers analyze-release-go-versionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/golang/skills/analyze-release-go-versions .github/skills/analyze-release-go-versions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyze-release-go-versions" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versions into .github/skills/analyze-release-go-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-release-go-versions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers analyze-release-go-versions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/golang/skills/analyze-release-go-versions .opencode/skills/analyze-release-go-versions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyze-release-go-versions" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/golang/skills/analyze-release-go-versions into .opencode/skills/analyze-release-go-versions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-release-go-versions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyze-release-go-versions- GitHub stars
- 120
- Token cost
- ~929 tokens
- SKILL.md length
- 411 words
- Files
- 1
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyze Go builder images, declared Go versions, or Go module versions across an OpenShift release using the golang plugin's release inventory scripts.
- The user asks to filter
- Calls python3
- Compare component results
What it does
Analyze Release Go Versions is an agent skill from openshift-eng/ai-helpers. Analyze Go builder images, declared Go versions, or Go module versions across an OpenShift release using the golang plugin's release inventory scripts. Use when the user asks to filter or compare component results.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with Go and Docker. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
When your agent uses it
- The user asks to filter
- Compare component results
Example prompts
- “/analyze-release-go-versions”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyze Release Go Versions loads about 929 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 411 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 411 words, ~929 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-release-go-versions/SKILL.md (or your agent's skills folder).- name
- analyze-release-go-versions
- description
- Analyze Go builder images, declared Go versions, or Go module versions across an OpenShift release using the golang plugin's release inventory scripts. Use when the user asks to filter or compare component results.
Analyze release Go versions
Use only the scripts below to collect release data. Do not independently inspect registries, GitHub, repositories, Dockerfiles, go.mod files, or build configs. Your job is to interpret and filter script output for the user's question. If the user supplies output from these scripts, analyze that output directly.
Run from the repository root, replacing placeholders with the user's values:
python3 plugins/golang/scripts/release_go_builder_versions.py <release-image> --correlate-builder --build-root
python3 plugins/golang/scripts/release_go_builder_versions.py <release-image> --correlate-builder
python3 plugins/golang/scripts/release_go_builder_versions.py <release-image> --build-root
python3 plugins/golang/scripts/release_go_module_versions.py <release-image> <module>
python3 plugins/golang/scripts/release_go_module_versions.py <release-image> --go-version<module> is the full Go module path the user is asking about (e.g. google.golang.org/protobuf, golang.org/x/net, k8s.io/client-go — any valid module works).
- Run only the needed script and mode.
--correlate-builderscans Dockerfiles or Containerfiles selected by release image build configs, including distinct OKD variants. Omit it only when the user wants all matching files in each source repository.--build-rootreports Go versions from each component's.ci-operator.yamlbuild root image tag (e.g.rhel-9-release-golang-1.26-openshift-5.0→1.26). This shows the CI build environment Go version, which may differ from the Dockerfile builder.- Combine both flags (
--correlate-builder --build-root) when the user asks about both Dockerfile builders and CI build roots. This avoids a redundant pass over the release — both lookups share the same source-repo resolution. The combined output appendsbuild root tagandbuild root go versioncolumns to each Dockerfile row. Prefer the combined form when both kinds of evidence are needed. - Used alone,
--build-rootproduces a compact 4-column output (component, repository, build root tag, go version) without Dockerfile scanning. - The builder script explicitly maps the two installer artifact components to build-data configs without
payload_name. Fornutanix-cluster-api-controllers, it scansopenshift/Dockerfile.openshiftin the source repository at the release-recorded ref when no build-data config matches; identify that row as source-repository evidence. - For a requested module, use its exact Go module path (e.g.
google.golang.org/grpc). Use--go-versiononly when the user asks aboutgodirectives ingo.mod. Run multiple scripts when the question needs both kinds of evidence. - Filter by component, repository, version, or variant as requested. Treat every returned row as separate evidence; the module script can return multiple rows per component and does not identify the
go.modpath in its output. - Preserve
(none), unknown values, and lookup errors as unknown or unavailable. Report module replacements as declared in script output, including local paths and fork modules. A builder tag such asgolang-1.26identifies the declared builder image version; agodirective or module declaration does not prove which compiler built the final image or which module version its binary contains. - Report the filtered results and any material coverage gaps. Do not fill gaps by fetching data yourself.
© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/golang/skills/analyze-release-go-versions of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Compare with similar skills
Analyze Release Go Versions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyze Release Go Versions this skillopenshift-eng/ai-helpers | 120 | — | ~929 | Automated safety check: Pass | Apache-2.0 | |
| Deploy Observabilityaliyun/alibabacloud-observability-mcp-server | 166 | — | ~2.6k | Automated safety check: Notes | None | |
| Censorship Audithedioum/Hedioum-Pool-Tunnel | 139 | — | ~4.9k | Automated safety check: Pass | GPL-3.0 | |
| Devinggo Generatorhuagelong/devinggo | 122 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Shopware CLI Dockershopware/shopware-cli | 124 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Deployment and CI/CD Patternsaffaan-m/ECC | 276k | 6 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Censorship Audit
hedioum/Hedioum-Pool-Tunnel
Audit and harden the Hedioum Pool Tunnel against nation-state DPI and censorship, as a filtering/anti-censorship expert would.
Devinggo Generator
huagelong/devinggo
DevingGo 代码生成器 CLI 工具集。当用户需要生成 CRUD 代码、创建模块、管理 Worker 任务、 导入导出模块、或需要快速搭建后端/前端代码时使用。适用于任何涉及代码生成、模块管理、 数据库表对应的前后端代码生成的场景。
Shopware CLI Docker
shopware/shopware-cli
A skill your agent uses when working on Docker-backed Shopware projects and needing to run Shopware or Symfony CLI commands, interact with project services or databases, start or stop the…
Deployment and CI/CD Patterns
affaan-m/ECC
Covers rolling, blue-green and canary deployments, multi-stage Dockerfiles, a GitHub Actions pipeline, health checks and production readiness for web apps.
Educates Upgrade Go
educates/educates-training-platform
Upgrade the Go version across the entire educates-training-platform project.
More from openshift-eng/ai-helpers
All 118 skills in this repoInvestigate CI Reliability
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
Address Review PR
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
Categorize Activity Types
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
Has Review Work
openshift-eng/ai-helpers
Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.
Must Gather Analyzer
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
Payload Autodl JSON
openshift-eng/ai-helpers
Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file
Related
Categories
Questions about Analyze Release Go Versions
What does Analyze Release Go Versions do?
Analyze Go builder images, declared Go versions, or Go module versions across an OpenShift release using the golang plugin's release inventory scripts. Analyze Release Go Versions is an agent skill from openshift-eng/ai-helpers. Analyze Go builder images, declared Go versions, or Go module versions across an OpenShift release using the golang plugin's release inventory scripts.
When should I use Analyze Release Go Versions?
Analyze Release Go Versions fits situations like: the user asks to filter; compare component results.
How do I install Analyze Release Go Versions in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a claude-code`. Or copy the skill folder (plugins/golang/skills/analyze-release-go-versions in openshift-eng/ai-helpers) into .claude/skills/analyze-release-go-versions in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Release Go Versions in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a codex`. Or copy the skill folder (plugins/golang/skills/analyze-release-go-versions in openshift-eng/ai-helpers) into .agents/skills/analyze-release-go-versions in your project. Codex loads it when a task matches its description.
Can I use Analyze Release Go Versions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill analyze-release-go-versions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-release-go-versions, .gemini/skills/analyze-release-go-versions, .github/skills/analyze-release-go-versions and .opencode/skills/analyze-release-go-versions in your project.
What does Analyze Release Go Versions need to run?
Going by SKILL.md and its folder, Analyze Release Go Versions needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Analyze Release Go Versions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyze Release Go Versions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analyze Release Go Versions use?
Analyze Release Go Versions is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyze Release Go Versions use?
About 929 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyze Release Go Versions?
Skills that share tags, products or a category with Analyze Release Go Versions: Deploy Observability (aliyun/alibabacloud-observability-mcp-server, 166 stars), Censorship Audit (hedioum/Hedioum-Pool-Tunnel, 139 stars), Devinggo Generator (huagelong/devinggo, 122 stars) and Shopware CLI Docker (shopware/shopware-cli, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Release Go Versions?
openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.
Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.