How do I install the Step Finder skill?

Run npx skillmds@latest add openshift/step-finder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Step Finder safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Step Finder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Step Finder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Step Finder?

openshift (@openshift) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Step Finder by openshift — Agent Skill

Name: Step Finder
Author: openshift

Step Finder

Search openshift/release step-registry for existing steps, workflows, and chains before creating new CI components. Use when adding tests, jobs, or step-registry entries, or when asked to find reusable pre/test/post components.

openshift f1be3c0 2.0 KB Updated Sep 17, 2026

File contents

Step Registry Search

Search 4,400+ step-registry components before creating duplicates.

When to use

Adding a CI test or job that needs ref, chain, or workflow
Creating a new step-registry component
Checking blast radius before editing an existing step

Run the search script

From repo root:

python3 .claude/scripts/step_finder.py "<query>" [--type step|workflow|chain|all] [--show-usage] [--no-reverse-deps] [--limit N]

Examples:

python3 .claude/scripts/step_finder.py "aws upgrade" --type workflow
python3 .claude/scripts/step_finder.py "install operator" --type step --show-usage
python3 .claude/scripts/step_finder.py openshift-e2e-test --no-reverse-deps

All query tokens must match (name, path, or documentation).

After results

Read the YAML and *-commands.sh for top matches — do not guess behavior.
Prefer reuse over new steps/workflows/chains.
Reference in ci-operator/config/<org>/<repo>/:
- step → - ref: <name>
- chain → - chain: <name>
- workflow → workflow: <name>
Regenerate artifacts: make update
Validate: make validate-step-registry and make checkconfig

Component types

Type	Files	Config reference
step	`-ref.yaml` + `-commands.sh`	`ref:`
chain	`*-chain.yaml`	`chain:`
workflow	`*-workflow.yaml` (`pre`/`test`/`post`)	`workflow:`

Impact from reverse deps

HIGH (100+): coordinate changes carefully
MEDIUM (10–99): test widely used components thoroughly
LOW (1–9): limited usage
NONE (0): top-level workflow or unused

Do not duplicate

Always run this skill before adding step-registry files. If a close match exists, extend it with env vars or compose it in a chain/workflow instead of copying.

---name: step-finderdescription: Search openshift/release step-registry for existing steps, workflows, and chains before creating new CI components. Use when adding tests, jobs, or step-registry entries, or when asked to find reusable pre/test/post components.---# Step Registry SearchSearch 4,400+ step-registry components before creating duplicates.## When to use- Adding a CI test or job that needs `ref`, `chain`, or `workflow`- Creating a new step-registry component- Checking blast radius before editing an existing step## Run the search scriptFrom repo root:```bashpython3 .claude/scripts/step_finder.py "<query>" [--type step|workflow|chain|all] [--show-usage] [--no-reverse-deps] [--limit N]```Examples:```bashpython3 .claude/scripts/step_finder.py "aws upgrade" --type workflowpython3 .claude/scripts/step_finder.py "install operator" --type step --show-usagepython3 .claude/scripts/step_finder.py openshift-e2e-test --no-reverse-deps```All query tokens must match (name, path, or documentation).## After results1. Read the YAML and `*-commands.sh` for top matches — do not guess behavior.2. Prefer reuse over new steps/workflows/chains.3. Reference in `ci-operator/config/<org>/<repo>/`: - step → `- ref: <name>` - chain → `- chain: <name>` - workflow → `workflow: <name>`4. Regenerate artifacts: `make update`5. Validate: `make validate-step-registry` and `make checkconfig`## Component types| Type | Files | Config reference ||------|-------|------------------|| step | `*-ref.yaml` + `*-commands.sh` | `ref:` || chain | `*-chain.yaml` | `chain:` || workflow | `*-workflow.yaml` (`pre`/`test`/`post`) | `workflow:` |## Impact from reverse deps- **HIGH** (100+): coordinate changes carefully- **MEDIUM** (10–99): test widely used components thoroughly- **LOW** (1–9): limited usage- **NONE** (0): top-level workflow or unused## Do not duplicateAlways run this skill before adding step-registry files. If a close match exists, extend it with env vars or compose it in a chain/workflow instead of copying.

Frequently asked questions