Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
End-to-end workflow from cluster data to deviation reports and optional Jira follow-up
Apache-2.0Auto-check passed
Install Rds Analyzer Workflow
$ npx skills add openshift-eng/ai-helpers --skill rds-analyzer-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers rds-analyzer-workflow --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/rds-analyzer/skills/rds-analyzer-workflow .claude/skills/rds-analyzer-workflow && 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 "rds-analyzer-workflow" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/rds-analyzer/skills/rds-analyzer-workflow into .claude/skills/rds-analyzer-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rds-analyzer-workflow", 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/rds-analyzer/skills/rds-analyzer-workflowType 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 rds-analyzer-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers rds-analyzer-workflow --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/rds-analyzer/skills/rds-analyzer-workflow .agents/skills/rds-analyzer-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rds-analyzer-workflow" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/rds-analyzer/skills/rds-analyzer-workflow into .agents/skills/rds-analyzer-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rds-analyzer-workflow", 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 rds-analyzer-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers rds-analyzer-workflow --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/rds-analyzer/skills/rds-analyzer-workflow .cursor/skills/rds-analyzer-workflow && 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 "rds-analyzer-workflow" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/rds-analyzer/skills/rds-analyzer-workflow into .cursor/skills/rds-analyzer-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rds-analyzer-workflow", 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/rds-analyzer/skills/rds-analyzer-workflow--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 rds-analyzer-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers rds-analyzer-workflow --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/rds-analyzer/skills/rds-analyzer-workflow .gemini/skills/rds-analyzer-workflow && 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 "rds-analyzer-workflow" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/rds-analyzer/skills/rds-analyzer-workflow into .gemini/skills/rds-analyzer-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rds-analyzer-workflow", 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 rds-analyzer-workflowInstalls 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 rds-analyzer-workflow -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/rds-analyzer/skills/rds-analyzer-workflow .github/skills/rds-analyzer-workflow && 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 "rds-analyzer-workflow" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/rds-analyzer/skills/rds-analyzer-workflow into .github/skills/rds-analyzer-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rds-analyzer-workflow", 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 rds-analyzer-workflow -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 rds-analyzer-workflow --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/rds-analyzer/skills/rds-analyzer-workflow .opencode/skills/rds-analyzer-workflow && 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 "rds-analyzer-workflow" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/rds-analyzer/skills/rds-analyzer-workflow into .opencode/skills/rds-analyzer-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rds-analyzer-workflow", 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
rds-analyzer-workflow- GitHub stars
- 120
- Token cost
- ~1.4k tokens
- SKILL.md length
- 382 words
- Files
- 1
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
End-to-end workflow from cluster data to deviation reports and optional Jira follow-up
- Works in 3 steps: Must-gather (or live cluster access via… → cluster-compare (kube-compare) plugin —… → Telco reference — pick RAN DU, Telco…
- SKILL.md covers Prerequisites (workflow context), Upstream rds-analyzer CLI…, Workflow scenarios (map to… and Helper script (optional), plus 4 more sections
- Calls podman
What it does
Rds Analyzer Workflow is an agent skill from openshift-eng/ai-helpers. End-to-end workflow from cluster data to deviation reports and optional Jira follow-up
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Jira. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
Example prompts
- “/rds-analyzer-workflow”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Must-gather (or live cluster access via kubeconfig) — see Red Hat docs for oc adm must-gather.
- cluster-compare (kube-compare) plugin — produces the JSON input RDS Analyzer consumes. Install per OCP docs and upstream kube-compare.
- Telco reference — pick RAN DU, Telco Core, or Telco Hub; run comparison per product docs so output is JSON (e.g. --output json where…
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:
podman
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.comdocs.redhat.com
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
Rds Analyzer Workflow loads about 1.4k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 382 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). 382 words, ~1,378 tokens.
Download SKILL.mdSave it as
.claude/skills/rds-analyzer-workflow/SKILL.md (or your agent's skills folder).- name
- rds-analyzer-workflow
- description
- End-to-end workflow from cluster data to deviation reports and optional Jira follow-up
RDS Analyzer workflow skill
Use this skill when guiding users through the end-to-end workflow from cluster data to deviation reports and optional Jira follow-up. It mirrors rds-analyzer docs/full-workflow.md and matches the current openshift-kni/rds-analyzer CLI (internal/cli/root.go, README.md).
Prerequisites (workflow context)
- Must-gather (or live cluster access via kubeconfig) — see Red Hat docs for
oc adm must-gather. - cluster-compare (kube-compare) plugin — produces the JSON input RDS Analyzer consumes. Install per OCP docs and upstream kube-compare.
- Telco reference — pick RAN DU, Telco Core, or Telco Hub; run comparison per product docs so output is JSON (e.g.
--output jsonwhere applicable).
Upstream rds-analyzer CLI (single command)
The repo exposes one executable with no subcommands: rds-analyzer [flags]. Cobra also provides --help / -h and --version / -v.
| Flag | Short | Default | Purpose |
|---|---|---|---|
--input | -i | stdin if not set | Path to kube-compare JSON. Without -i, data must be piped to stdin; interactive stdin with no pipe fails fast. |
--rules | -r | ./rules.yaml | Path to one rules YAML file. |
--output | -o | text | text or html only. |
--output-mode | -m | simple | simple or reporting. |
--target | -t | (empty) | OCP version for rules (e.g. 4.19). If empty, highest version in rules is used. |
--validate-rules-only | — | false | Validate regexp patterns in rules; no JSON input; do not use with -i. |
Examples (from upstream README / CLI help)
cat results.json | rds-analyzer -r /path/to/custom-rules.yaml
rds-analyzer -r ran-du-rules.yaml --validate-rules-only
rds-analyzer -i results.json -o html > report.html
rds-analyzer -i results.json -t 4.19
rds-analyzer -i results.json -r /path/to/rules.yaml
rds-analyzer -i results.json -m reporting
rds-analyzer --help
rds-analyzer --versionContainer (README)
podman run --rm -v $(pwd):/data:Z quay.io/rhsysdeseng/rds-analyzer:latest \
-i /data/results.json -r /data/rules.yamlWorkflow scenarios (map to user requests)
A. Text report (terminal)
rds-analyzer -i comparison-results.json -r example-ran-du-rules.yamlEquivalent defaults: -o text -m simple.
Show full SKILL.md (154 more words)Show less
B. HTML report
rds-analyzer -i comparison-results.json -r example-ran-du-rules.yaml -o html > deviation-report.htmlC. Specific OCP version + rules path
rds-analyzer -i comparison-results.json -o html -t 4.21 -r /path/to/rules.yaml > deviation-report.htmlD. Reporting mode (LLM / Jira prep)
rds-analyzer -i comparison-results.json -r example-ran-du-rules.yaml -m reportingE. Stdin
cat comparison-results.json | rds-analyzer -r rules.yamlF. Validate rules only
rds-analyzer -r ran-du-rules.yaml --validate-rules-onlyHelper script (optional)
From the ai-helpers repo, after chmod +x:
plugins/rds-analyzer/scripts/run_rds_analyzer.sh
text→-o text -m simplehtml→-o html -m simplereporting→-o text -m reportingvalidate-rules→--validate-rules-only(matches upstream flag name)
Example:
export RDS_ANALYZER_BIN=/path/to/rds-analyzer
./plugins/rds-analyzer/scripts/run_rds_analyzer.sh text -- -i results.json -r rules.yaml
./plugins/rds-analyzer/scripts/run_rds_analyzer.sh validate-rules -- -r rules.yamlReference documentation links (cluster compare / telco)
After the report: Jiras
Use deviation output to open or track issues. In ai-helpers, the jira plugin can assist with creating or structuring issues from structured text; combine reporting mode output with /jira:create or related commands when deviations require tracking or resolution.
Example rules path in rds-analyzer repo
examples/example-ran-du-rules.yaml (relative to a clone of openshift-kni/rds-analyzer).
Rules engine reminders
- Worst impact wins: Impacting > NeedsReview > NotImpacting > NotADeviation.
- Regex in rules is validated at startup; invalid patterns fail before JSON is read (unless
--validate-rules-onlyalone).
© 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/rds-analyzer/skills/rds-analyzer-workflow of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Compare with similar skills
Rds Analyzer Workflow 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 |
|---|---|---|---|---|---|---|
| Rds Analyzer Workflow this skillopenshift-eng/ai-helpers | 120 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| YugabyteDB Issue Creatoryugabyte/yugabyte-db | 11k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewcroffasia/itsaplan | 895 | — | ~2k | Automated safety check: Pass | AGPL-3.0 | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None |
Similar skills
YugabyteDB Issue Creator
yugabyte/yugabyte-db
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Code Review
croffasia/itsaplan
A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
- Official
PR Body
SAP/spartacus
A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.
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
Works with
Questions about Rds Analyzer Workflow
What does Rds Analyzer Workflow do?
End-to-end workflow from cluster data to deviation reports and optional Jira follow-up. Rds Analyzer Workflow is an agent skill from openshift-eng/ai-helpers.
How do I install Rds Analyzer Workflow in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill rds-analyzer-workflow -a claude-code`. Or copy the skill folder (plugins/rds-analyzer/skills/rds-analyzer-workflow in openshift-eng/ai-helpers) into .claude/skills/rds-analyzer-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Rds Analyzer Workflow in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill rds-analyzer-workflow -a codex`. Or copy the skill folder (plugins/rds-analyzer/skills/rds-analyzer-workflow in openshift-eng/ai-helpers) into .agents/skills/rds-analyzer-workflow in your project. Codex loads it when a task matches its description.
Can I use Rds Analyzer Workflow 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 rds-analyzer-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rds-analyzer-workflow, .gemini/skills/rds-analyzer-workflow, .github/skills/rds-analyzer-workflow and .opencode/skills/rds-analyzer-workflow in your project.
What does Rds Analyzer Workflow need to run?
Going by SKILL.md and its folder, Rds Analyzer Workflow needs the command-line tools its instructions call (podman).
Does Rds Analyzer Workflow access the network?
SKILL.md names 2 domains. As links in the text: github.com and docs.redhat.com. This is read from the text; nothing was executed.
Is Rds Analyzer Workflow 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 Rds Analyzer Workflow use?
Rds Analyzer Workflow 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 Rds Analyzer Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Rds Analyzer Workflow?
Skills that share tags, products or a category with Rds Analyzer Workflow: Management Talk (thananon/9arm-skills, 3.2k stars), YugabyteDB Issue Creator (yugabyte/yugabyte-db, 11k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Code Review (croffasia/itsaplan, 895 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rds Analyzer Workflow?
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.