PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
A skill your agent uses when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data.
Apache-2.0Auto-check passed
Install Generate Okd CI Operator Configs
$ npx skills add openshift-eng/ai-helpers --skill generate-okd-ci-operator-configs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers generate-okd-ci-operator-configs --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/ci/skills/generate-okd-ci-operator-configs .claude/skills/generate-okd-ci-operator-configs && 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 "generate-okd-ci-operator-configs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/generate-okd-ci-operator-configs into .claude/skills/generate-okd-ci-operator-configs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-okd-ci-operator-configs", 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/ci/skills/generate-okd-ci-operator-configsType 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 generate-okd-ci-operator-configs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers generate-okd-ci-operator-configs --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/ci/skills/generate-okd-ci-operator-configs .agents/skills/generate-okd-ci-operator-configs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "generate-okd-ci-operator-configs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/generate-okd-ci-operator-configs into .agents/skills/generate-okd-ci-operator-configs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-okd-ci-operator-configs", 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 generate-okd-ci-operator-configs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers generate-okd-ci-operator-configs --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/ci/skills/generate-okd-ci-operator-configs .cursor/skills/generate-okd-ci-operator-configs && 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 "generate-okd-ci-operator-configs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/generate-okd-ci-operator-configs into .cursor/skills/generate-okd-ci-operator-configs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-okd-ci-operator-configs", 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/ci/skills/generate-okd-ci-operator-configs--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 generate-okd-ci-operator-configs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers generate-okd-ci-operator-configs --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/ci/skills/generate-okd-ci-operator-configs .gemini/skills/generate-okd-ci-operator-configs && 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 "generate-okd-ci-operator-configs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/generate-okd-ci-operator-configs into .gemini/skills/generate-okd-ci-operator-configs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-okd-ci-operator-configs", 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 generate-okd-ci-operator-configsInstalls 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 generate-okd-ci-operator-configs -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/ci/skills/generate-okd-ci-operator-configs .github/skills/generate-okd-ci-operator-configs && 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 "generate-okd-ci-operator-configs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/generate-okd-ci-operator-configs into .github/skills/generate-okd-ci-operator-configs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-okd-ci-operator-configs", 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 generate-okd-ci-operator-configs -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 generate-okd-ci-operator-configs --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/ci/skills/generate-okd-ci-operator-configs .opencode/skills/generate-okd-ci-operator-configs && 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 "generate-okd-ci-operator-configs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/generate-okd-ci-operator-configs into .opencode/skills/generate-okd-ci-operator-configs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-okd-ci-operator-configs", 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
generate-okd-ci-operator-configs- GitHub stars
- 120
- Token cost
- ~1.5k tokens
- SKILL.md length
- 617 words
- Files
- 8
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data.
- Works in 4 steps: Locate the bundled helper → Clone ocp-build-data (if not already… → Validate inputs and run the generator → …
- You need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data
- SKILL.md covers Arguments, Execution, Helper layout and Key resolution rules
- Runs Python scripts from its folder; calls python3, make and git; reaches github.com
What it does
Generate Okd CI Operator Configs is an agent skill from openshift-eng/ai-helpers. Use when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data. Replicates the logic of doozer's images:okd prs open command as a standalone tool.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `generate_okd_ci_configs.py`, `okd_ci_configs/__init__.py` and `okd_ci_configs/ci_operator.py`).
It works with GitHub. 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
- You need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data
Example prompts
- “/generate-okd-ci-operator-configs”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
python3makegit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.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
Generate Okd CI Operator Configs loads about 1.5k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 617 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). 617 words, ~1,517 tokens.
Download SKILL.mdSave it as
.claude/skills/generate-okd-ci-operator-configs/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- generate-okd-ci-operator-configs
- description
- Use when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data. Replicates the logic of doozer's `images:okd prs open` command as a standalone tool.
- argument-hint
- <ocp-build-data-path> <okd-version> [--output-dir <path>] [--github-token <token>] [--dry-run]
Generate OKD/SCOS ci-operator configuration YAML files for the openshift/release repository from ART image metadata using the bundled Python generator.
Arguments
Parse from: $ARGUMENTS
- First argument: path to the ocp-build-data directory (must contain
group.yml,streams.yml,images/). - Second argument: OKD version string (e.g.
4.18,5.0). --output-dir <path>: Directory to write ci-operator configs (default for this skill:./okd-ci-configs). In an openshift/release checkout, use itsci-operator/config/directory.--github-token <token>: Optional GitHub token for downloading upstream Dockerfiles. Requests are unauthenticated when omitted.--dry-run: Print generated YAML without writing files. Upstream Dockerfiles are still downloaded.
If no arguments are provided, look for ocp-build-data at ./tmp-dir/ocp-build-data/ or ../ocp-build-data/, and derive the OKD version from group.yml vars (MAJOR.MINOR). Use build data for the requested release; the OKD version argument controls the destination imagestream and does not change the metadata's branches.
Execution
1. Locate the bundled helper
Set SKILL_DIR to the absolute directory containing this SKILL.md. The entry point is generate_okd_ci_configs.py alongside this file.
- In this repository, the skill directory is
.claude/skills/generate-okd-ci-operator-configs-with-helper-script/. - In the ai-helpers CI plugin, it is
${CLAUDE_PLUGIN_ROOT}/skills/generate-okd-ci-operator-configs/.
The entry point imports the sibling okd_ci_configs package. Keep the whole skill directory together when installing or copying it. Running the entry point by its absolute path works from any working directory without setting PYTHONPATH or installing the helper package.
Python 3, PyYAML, and requests are required. Use the project's virtual environment if available. Check dependencies with:
python3 -c 'import yaml, requests'2. Clone ocp-build-data (if not already present)
If the ocp-build-data directory is not provided or does not exist locally, clone it from GitHub:
git clone https://github.com/openshift-eng/ocp-build-data.git --branch openshift-$OKD_VERSIONThe branch should match the target OKD version (e.g. openshift-5.0 for OKD 5.0, openshift-4.18 for OKD 4.18).
3. Validate inputs and run the generator
Verify the build-data directory contains group.yml, streams.yml, and images/. Resolve the arguments into OCP_BUILD_DATA_PATH, OKD_VERSION, and OUTPUT_DIR; pass ./okd-ci-configs explicitly when the skill's output default is used, since the Python CLI requires --output-dir.
python3 "$SKILL_DIR/generate_okd_ci_configs.py" \
--ocp-build-data "$OCP_BUILD_DATA_PATH" \
--okd-version "$OKD_VERSION" \
--output-dir "$OUTPUT_DIR"Append --github-token with the provided token or --dry-run when requested.
The generator reads and substitutes ART metadata, resolves payload dependencies, downloads upstream Dockerfiles, and writes one config per (org, repo, branch) to:
{output-dir}/{org}/{repo}/{org}-{repo}-{branch}__okd-scos.yamlIt handles okd_alignment overrides for parent images, Dockerfiles, source paths, context directories, build arguments, build roots, and RPM repository injection.
Show full SKILL.md (257 more words)Show less
4. Report results
Report the generated config count, output paths, skipped images with reasons, and warnings or errors. A successful invocation can still skip images or refuse incomplete repository configs; include those limitations in the report.
For configs generated into an openshift/release checkout, the follow-up generation commands are make ci-operator-configs and make jobs.
Helper layout
The entry point owns argument parsing and input validation. Read the relevant module when diagnosing or changing a specific part of generation:
| Module | Responsibility |
|---|---|
| helpers.py | Git URL normalization, public upstream mappings, variable substitution, and CI image coordinates |
| metadata.py | Load image metadata, resolve OKD tags and pullspecs, and find payload dependencies |
| dockerfiles.py | Download upstream Dockerfiles and parse FROM instructions |
| ci_operator.py | Build image/repository configurations and serialize ci-operator YAML |
| generator.py | Orchestrate loading, reconciliation, generation, and result reporting |
When copying this skill into ai-helpers, use plugins/ci/skills/generate-okd-ci-operator-configs/ and set the frontmatter name to generate-okd-ci-operator-configs to match that directory. The helper package needs no plugin manifest registration.
Key resolution rules
- Streams resolve in order:
okd.resolve_as.image,upstream_image, thenimage. - Images with
okd_alignment.resolve_as.streamor.imageuse the resolved pullspec and are not built by this generator. - Otherwise, images use
registry.ci.openshift.org/origin/scos-{version}:{tag}. The tag comes fromokd_alignment.tag_name, orpayload_name/namewith theose-prefix stripped. - Public upstream URLs use the longest matching
public_upstreamsmapping ingroup.yml. A mapping'spublic_branchoverrides the source branch; otherwise the source branch is used, withmainas the fallback when absent. - Images explicitly disabled for OKD, lacking usable source or parent metadata, or unnecessary for the payload are skipped. Dockerfile download failures and parent-count mismatches also skip images.
© 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
SKILL.md and 7 other files in plugins/ci/skills/generate-okd-ci-operator-configs of openshift-eng/ai-helpers.
- SKILL.md
- generate_okd_ci_configs.py
- okd_ci_configs/__init__.py
- okd_ci_configs/ci_operator.py
- okd_ci_configs/dockerfiles.py
- okd_ci_configs/generator.py
- okd_ci_configs/helpers.py
- okd_ci_configs/metadata.py
Open the folder on GitHubat commit a627176
Compare with similar skills
Generate Okd CI Operator Configs 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 |
|---|---|---|---|---|---|---|
| Generate Okd CI Operator Configs this skillopenshift-eng/ai-helpers | 120 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Diagnosing Superpowers Sessionsobra/superpowers | 297k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Generate Okd CI Operator Configs
What does Generate Okd CI Operator Configs do?
A skill your agent uses when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data. Generate Okd CI Operator Configs is an agent skill from openshift-eng/ai-helpers. Use when you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data.
When should I use Generate Okd CI Operator Configs?
Generate Okd CI Operator Configs fits situations like: you need to generate OKD/SCOS ci-operator configuration YAML files from ART ocp-build-data.
How do I install Generate Okd CI Operator Configs in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill generate-okd-ci-operator-configs -a claude-code`. Or copy the skill folder (plugins/ci/skills/generate-okd-ci-operator-configs in openshift-eng/ai-helpers) into .claude/skills/generate-okd-ci-operator-configs in your project. Claude Code loads it when a task matches its description.
How do I install Generate Okd CI Operator Configs in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill generate-okd-ci-operator-configs -a codex`. Or copy the skill folder (plugins/ci/skills/generate-okd-ci-operator-configs in openshift-eng/ai-helpers) into .agents/skills/generate-okd-ci-operator-configs in your project. Codex loads it when a task matches its description.
Can I use Generate Okd CI Operator Configs 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 generate-okd-ci-operator-configs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-okd-ci-operator-configs, .gemini/skills/generate-okd-ci-operator-configs, .github/skills/generate-okd-ci-operator-configs and .opencode/skills/generate-okd-ci-operator-configs in your project.
What does Generate Okd CI Operator Configs need to run?
Going by SKILL.md and its folder, Generate Okd CI Operator Configs needs Python for the scripts in its folder and the command-line tools its instructions call (python3, make and git). Our summary lists: Python 3.
Does Generate Okd CI Operator Configs access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Generate Okd CI Operator Configs 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 Generate Okd CI Operator Configs use?
Generate Okd CI Operator Configs 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 Generate Okd CI Operator Configs use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Generate Okd CI Operator Configs?
Skills that share tags, products or a category with Generate Okd CI Operator Configs: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Generate Okd CI Operator Configs?
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.