Technical Job Search
github/awesome-copilot
A skill your agent uses when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV/resume, writing a cover letter, evaluating a job offer…
List Prow job runs from the Sippy API using its real filter syntax — find run IDs by job name, variant, result, or time window
Apache-2.0Auto-check passed
Install Fetch Prow Job Runs
$ npx skills add openshift-eng/ai-helpers --skill fetch-prow-job-runs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prow-job-runs --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/fetch-prow-job-runs .claude/skills/fetch-prow-job-runs && 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 "fetch-prow-job-runs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prow-job-runs into .claude/skills/fetch-prow-job-runs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prow-job-runs", 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/fetch-prow-job-runsType 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 fetch-prow-job-runs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prow-job-runs --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/fetch-prow-job-runs .agents/skills/fetch-prow-job-runs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fetch-prow-job-runs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prow-job-runs into .agents/skills/fetch-prow-job-runs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prow-job-runs", 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 fetch-prow-job-runs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prow-job-runs --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/fetch-prow-job-runs .cursor/skills/fetch-prow-job-runs && 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 "fetch-prow-job-runs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prow-job-runs into .cursor/skills/fetch-prow-job-runs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prow-job-runs", 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/fetch-prow-job-runs--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 fetch-prow-job-runs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prow-job-runs --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/fetch-prow-job-runs .gemini/skills/fetch-prow-job-runs && 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 "fetch-prow-job-runs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prow-job-runs into .gemini/skills/fetch-prow-job-runs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prow-job-runs", 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 fetch-prow-job-runsInstalls 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 fetch-prow-job-runs -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/fetch-prow-job-runs .github/skills/fetch-prow-job-runs && 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 "fetch-prow-job-runs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prow-job-runs into .github/skills/fetch-prow-job-runs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prow-job-runs", 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 fetch-prow-job-runs -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 fetch-prow-job-runs --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/fetch-prow-job-runs .opencode/skills/fetch-prow-job-runs && 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 "fetch-prow-job-runs" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prow-job-runs into .opencode/skills/fetch-prow-job-runs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prow-job-runs", 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
fetch-prow-job-runs- GitHub stars
- 120
- Token cost
- ~1.7k tokens
- SKILL.md length
- 644 words
- Files
- 3
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
List Prow job runs from the Sippy API using its real filter syntax — find run IDs by job name, variant, result, or time window
- Works in 2 steps: Network Access: The Sippy API must be… → Python 3: Python 3.6 or later, standard…
- SKILL.md covers When to Use This Skill, Prerequisites, Implementation Steps and API Details, plus 4 more sections
- Runs Python scripts from its folder; calls python3; reaches sippy.dptools.openshift.org
What it does
Fetch Prow Job Runs is an agent skill from openshift-eng/ai-helpers. List Prow job runs from the Sippy API using its real filter syntax — find run IDs by job name, variant, result, or time window
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `fetch_prow_job_runs.py` and `test_fetch_prow_job_runs.py`).
The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
Example prompts
- “/fetch-prow-job-runs”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Network Access: The Sippy API must be accessible at https://sippy.dptools.openshift.org
- Python 3: Python 3.6 or later, standard library only
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:
python3
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:
sippy.dptools.openshift.org
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
Fetch Prow Job Runs loads about 1.7k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 644 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). 644 words, ~1,693 tokens.
Download SKILL.mdSave it as
.claude/skills/fetch-prow-job-runs/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- fetch-prow-job-runs
- description
- List Prow job runs from the Sippy API using its real filter syntax — find run IDs by job name, variant, result, or time window
Fetch Prow Job Runs
Sippy Symptoms are known-failure signatures for OpenShift CI. A symptom is a rule made of a file pattern (a glob over a CI job run's artifact files, e.g. **/build-log.txt) and a matcher (string = substring, regex = regular expression, none = file merely exists, cel = a compound CEL expression over other label names). When a symptom matches a job run's artifacts, Sippy applies one or more Labels — human-readable tags like InfraFailure — to that run. Labels appear in the Sippy UI and Spyglass and help everyone quickly recognize known failure modes without re-debugging them. You do not need any prior Sippy knowledge to use this skill.
This skill finds Prow job runs (and their prow_id values) via the Sippy /api/jobs/runs endpoint. It exists because this API does not accept ad-hoc query parameters like ?job_name= or ?period= — those do not exist and will be silently ignored or rejected. Filtering is done through a JSON filter parameter with a fixed set of column fields and operators (listed below), and this skill's script builds that JSON with verified fields and operators so you never have to guess.
When to Use This Skill
Use this skill when you need to:
- Find run IDs (
prow_id) to feed intoreevaluate-job-runsafter creating or updating a symptom - Check how widespread a failure is (e.g. all failed runs of a job family in the last day)
- List recent runs matching a platform/network/etc. variant
- Get the Prow URL of recent runs of a given job
Prerequisites
- Network Access: The Sippy API must be accessible at
https://sippy.dptools.openshift.org- No authentication required
- Python 3: Python 3.6 or later, standard library only
Implementation Steps
Invoke the script with flags matching the question:
script_path="plugins/ci/skills/fetch-prow-job-runs/fetch_prow_job_runs.py"
# Metal-platform runs in the last 24 hours
python3 "$script_path" --release 5.0 --variant Platform:metal --since-hours 24 --format summary
# Failed runs of jobs whose name contains e2e-metal
python3 "$script_path" --release 5.0 --job-contains e2e-metal --result F --format summary
# Pipe run IDs into symptom reevaluation
python3 "$script_path" --release 5.0 --job-contains e2e-metal --result F --since-hours 48 --ids-only \
| xargs python3 plugins/ci/skills/reevaluate-job-runs/reevaluate_job_runs.py --dry-runFlags:
--release <release>(required): OpenShift release, e.g.5.0--job-contains <substr>(repeatable): job name must contain each substring--variant <Key:Value>(repeatable): run must have each variant entry, e.g.Platform:metal--result <code>: overall result code (Ssuccess,Ffailure,ninfra failure — lowercase n)--since-hours <n>: only runs newer than N hours ago--filter-json <raw>: escape hatch — raw JSON array of extra filter items merged with the generated ones--limit <n>: max rows (default 100)--ids-only: print justprow_idper line (pipeline-friendly)--format {json,summary}: output format (defaultjson)
All filter items are combined with AND.
API Details
Endpoint
GET https://sippy.dptools.openshift.org/api/jobs/runs?release={release}&filter={urlencoded_json}&limit={n}&sortField=timestamp&sort=descNo authentication required.
Filter JSON Shape
{"items": [{"columnField": "name", "operatorValue": "contains", "value": "e2e-metal"}], "linkOperator": "and"}Show full SKILL.md (261 more words)Show less
Verified Column Fields and Operators
Do NOT invent other query parameters or fields — only these are verified to work:
| columnField | operatorValue | value |
|---|---|---|
name | contains | job-name substring |
variants | has entry | Key:Value, e.g. Platform:metal |
timestamp | > / < | epoch milliseconds as a string |
overall_result | equals | S (success), F (failure), n (infra failure — lowercase) |
An unknown columnField yields HTTP 400 with a "column does not exist" message; the script surfaces that message verbatim.
Response Row Fields
{"rows": [...]}; each row has prow_id (string), job, url, variants[], overall_result, failed, succeeded, infrastructure_failure, test_failures, timestamp (epoch millis), cluster.
Error Handling
Case 1: Unknown Column (HTTP 400)
Error: HTTP 400 from Sippy API: {"code":400,"message":"could not filter or sort data: error updating query for filter ... column does not exist"}Use only the column fields in the table above. Exits 1.
Case 2: Network Error
Error: failed to connect to Sippy API: [Errno -2] Name or service not knownExits 1. Check connectivity to sippy.dptools.openshift.org.
Case 3: Empty Results
No matching runs prints [] (JSON), Total: 0 (summary), or nothing (--ids-only) and exits 0 — not an error.
Exit Codes:
0: Success (including empty results)1: Error (HTTP error, network error, invalid--filter-json)
Examples
Example 1: Metal Runs in the Last 24 Hours
python3 plugins/ci/skills/fetch-prow-job-runs/fetch_prow_job_runs.py \
--release 5.0 --variant Platform:metal --since-hours 24 --limit 5 --format summaryExpected Output (excerpt):
n periodic-ci-openshift-release-main-nightly-5.0-e2e-metal-ovn-ha-cert-rotation-shutdown-5y-age-90d 2080684960133419008 1784908873000
Total: 5Example 2: Failed Runs of a Job Family
python3 plugins/ci/skills/fetch-prow-job-runs/fetch_prow_job_runs.py \
--release 5.0 --job-contains e2e-metal --result F --format summaryExample 3: Feed Run IDs to Reevaluation
python3 plugins/ci/skills/fetch-prow-job-runs/fetch_prow_job_runs.py \
--release 5.0 --job-contains e2e-metal --since-hours 48 --ids-only \
| xargs python3 plugins/ci/skills/reevaluate-job-runs/reevaluate_job_runs.py --dry-runNotes
- Results are sorted newest-first (
sortField=timestamp&sort=desc) timestampfilter values must be epoch milliseconds (the script computes this for--since-hours)- Repeatable flags AND together; there is no OR support in this script (use
--filter-jsonif you need custom items)
See Also
- Related Skill:
reevaluate-job-runs(re-run symptom detection on the run IDs found here) - Related Skill:
diagnose-job-run-symptoms(explain which symptoms/labels apply to a run) - Related Skill:
list-symptoms(browse the symptom/label catalog) - Related Skill:
fetch-regression-details(another source of job run IDs, from regressions)
© 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 2 other files in plugins/ci/skills/fetch-prow-job-runs of openshift-eng/ai-helpers.
- SKILL.md
- fetch_prow_job_runs.py
- test_fetch_prow_job_runs.py
Open the folder on GitHubat commit a627176
Compare with similar skills
Fetch Prow Job Runs 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 |
|---|---|---|---|---|---|---|
| Fetch Prow Job Runs this skillopenshift-eng/ai-helpers | 120 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Technical Job Searchgithub/awesome-copilot | 40k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Job Application AssistantMadsLorentzen/ai-job-search | 45k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Job Application Managerreactive-resume/reactive-resume | 44k | — | ~13k | Automated safety check: Pass | MIT | |
| Python Background Jobswshobson/agents | 40k | — | ~1.8k | Automated safety check: Pass | MIT | |
| LobeHub Data Fetching Layerslobehub/lobehub | 83k | — | ~1.8k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Job Application Assistant
MadsLorentzen/ai-job-search
Evaluates job postings against your profile, then tailors a LaTeX CV and cover letter and prepares interview answers for the roles you pursue.
Job Application Manager
reactive-resume/reactive-resume
Runs the job-search pipeline. An agent skill from reactive-resume/reactive-resume.
Python Background Jobs
wshobson/agents
Python background job patterns including task queues, workers, and event-driven architecture.
LobeHub Data Fetching Layers
lobehub/lobehub
Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.
Steve Jobs
sickn33/agentic-awesome-skills
Agente que simula Steve Jobs — cofundador da Apple, CEO da Pixar, fundador da NeXT, o maior designer de produtos tecnologicos da historia e o mais influente apresentador de produtos do mundo.
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
Questions about Fetch Prow Job Runs
What does Fetch Prow Job Runs do?
List Prow job runs from the Sippy API using its real filter syntax — find run IDs by job name, variant, result, or time window. Fetch Prow Job Runs is an agent skill from openshift-eng/ai-helpers.
How do I install Fetch Prow Job Runs in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill fetch-prow-job-runs -a claude-code`. Or copy the skill folder (plugins/ci/skills/fetch-prow-job-runs in openshift-eng/ai-helpers) into .claude/skills/fetch-prow-job-runs in your project. Claude Code loads it when a task matches its description.
How do I install Fetch Prow Job Runs in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill fetch-prow-job-runs -a codex`. Or copy the skill folder (plugins/ci/skills/fetch-prow-job-runs in openshift-eng/ai-helpers) into .agents/skills/fetch-prow-job-runs in your project. Codex loads it when a task matches its description.
Can I use Fetch Prow Job Runs 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 fetch-prow-job-runs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fetch-prow-job-runs, .gemini/skills/fetch-prow-job-runs, .github/skills/fetch-prow-job-runs and .opencode/skills/fetch-prow-job-runs in your project.
What does Fetch Prow Job Runs need to run?
Going by SKILL.md and its folder, Fetch Prow Job Runs needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Fetch Prow Job Runs access the network?
SKILL.md names 1 domain. In commands or code: sippy.dptools.openshift.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Fetch Prow Job Runs 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 Fetch Prow Job Runs use?
Fetch Prow Job Runs 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 Fetch Prow Job Runs use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Fetch Prow Job Runs?
Skills that share tags, products or a category with Fetch Prow Job Runs: Technical Job Search (github/awesome-copilot, 40k stars), Job Application Assistant (MadsLorentzen/ai-job-search, 45k stars), Job Application Manager (reactive-resume/reactive-resume, 44k stars) and Python Background Jobs (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fetch Prow Job Runs?
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.