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…
Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL
Apache-2.0Auto-check passed
Install Fetch Prowjob JSON
$ npx skills add openshift-eng/ai-helpers --skill fetch-prowjob-json -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prowjob-json --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-prowjob-json .claude/skills/fetch-prowjob-json && 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-prowjob-json" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prowjob-json into .claude/skills/fetch-prowjob-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prowjob-json", 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-prowjob-jsonType 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-prowjob-json -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prowjob-json --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-prowjob-json .agents/skills/fetch-prowjob-json && 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-prowjob-json" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prowjob-json into .agents/skills/fetch-prowjob-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prowjob-json", 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-prowjob-json -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prowjob-json --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-prowjob-json .cursor/skills/fetch-prowjob-json && 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-prowjob-json" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prowjob-json into .cursor/skills/fetch-prowjob-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prowjob-json", 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-prowjob-json--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-prowjob-json -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers fetch-prowjob-json --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-prowjob-json .gemini/skills/fetch-prowjob-json && 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-prowjob-json" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prowjob-json into .gemini/skills/fetch-prowjob-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prowjob-json", 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-prowjob-jsonInstalls 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-prowjob-json -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-prowjob-json .github/skills/fetch-prowjob-json && 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-prowjob-json" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prowjob-json into .github/skills/fetch-prowjob-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prowjob-json", 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-prowjob-json -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-prowjob-json --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-prowjob-json .opencode/skills/fetch-prowjob-json && 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-prowjob-json" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-prowjob-json into .opencode/skills/fetch-prowjob-json/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-prowjob-json", 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-prowjob-json- GitHub stars
- 120
- Token cost
- ~2.1k tokens
- SKILL.md length
- 742 words
- Files
- 1
- Skills in repo
- 118
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL
- Works in 4 steps: Parse the Prow Job URL → Construct the GCS Web URL → Fetch the prowjob.json → …
- SKILL.md covers When to Use This Skill, Prerequisites, Implementation Steps and Error Handling, plus 3 more sections
- Calls curl; reaches gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com and prow.ci.openshift.org
What it does
Fetch Prowjob JSON is an agent skill from openshift-eng/ai-helpers. Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
Example prompts
- “/fetch-prowjob-json”
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
Shell commands in SKILL.md call:
curl
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:
gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.comprow.ci.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 Prowjob JSON loads about 2.1k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 742 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). 742 words, ~2,065 tokens.
Download SKILL.mdSave it as
.claude/skills/fetch-prowjob-json/SKILL.md (or your agent's skills folder).- name
- fetch-prowjob-json
- description
- Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL
Fetch ProwJob JSON
This skill fetches the prowjob.json artifact for a given Prow job and returns key fields including job metadata, spec details, status, and release annotations.
When to Use This Skill
Use this skill when you need to:
- Get metadata about a specific Prow job run (status, timing, cluster, pod name)
- Determine what payload a job was tested against (
release.openshift.io/tag) - Determine the upgrade source version for upgrade jobs (
release.openshift.io/from-tag) - Get the release images (
RELEASE_IMAGE_LATEST,RELEASE_IMAGE_INITIAL) used in a job - Check the ci-operator target and variant for a job
- Get the GCS bucket path for a job's artifacts
Prerequisites
- Network Access: Must be able to reach the GCS web proxy
- Check:
curl -s -o /dev/null -w '%{http_code}' https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/ - No authentication required
- Check:
Implementation Steps
Step 1: Parse the Prow Job URL
Extract the GCS path from the Prow job URL. Prow URLs follow this pattern:
https://prow.ci.openshift.org/view/gs/<bucket>/<path>/<job-name>/<build-id>Extract everything after /view/ to get the GCS reference:
gs/<bucket>/<path>/<job-name>/<build-id>Step 2: Construct the GCS Web URL
Convert the Prow URL to a gcsweb URL that serves the raw prowjob.json:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/<bucket>/<path>/<job-name>/<build-id>/prowjob.jsonExample:
- Input Prow URL:
https://prow.ci.openshift.org/view/gs/test-platform-results-public/logs/periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-upgrade/2019864414127132672 - GCS Web URL:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results-public/logs/periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-upgrade/2019864414127132672/prowjob.json
The conversion is: replace https://prow.ci.openshift.org/view/ with https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/ and append /prowjob.json.
Step 3: Fetch the prowjob.json
Use curl or WebFetch to retrieve the JSON content from the constructed URL.
curl -s "https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results-public/logs/<job-name>/<build-id>/prowjob.json"Step 4: Extract and Return Key Fields
From the full prowjob.json, extract and return the following fields:
Required Fields
| Field | JSON Path | Description |
|---|---|---|
| Job Name | spec.job | Full periodic/presubmit/postsubmit job name |
| Job Type | spec.type | periodic, presubmit, or postsubmit |
| Build ID | status.build_id | Unique build identifier |
| State | status.state | success, failure, aborted, pending, triggered |
| Description | status.description | Human-readable status description |
| Start Time | status.startTime | ISO 8601 timestamp |
| Completion Time | status.completionTime | ISO 8601 timestamp (null if still running) |
| Cluster | spec.cluster | Build cluster (e.g., build02, build05) |
| Pod Name | status.pod_name | Kubernetes pod name |
| Prow URL | status.url | Link back to the Prow job view |
| Payload Tag | metadata.annotations["release.openshift.io/tag"] | The payload version tested or upgraded to (e.g., 4.22.0-0.ci-2026-02-06-195709). This is the payload the cluster was tested against or upgraded to. |
| Upgrade From Tag | metadata.annotations["release.openshift.io/from-tag"] | The original payload version before upgrade (e.g., 4.22.0-0.ci-2026-02-05-195709). Only present for upgrade jobs. This is the version the cluster starts at before upgrading to the payload tag. |
| Release Source | metadata.annotations["release.openshift.io/source"] | Release stream source (e.g., ocp/4.22) |
| Architecture | metadata.annotations["release.openshift.io/architecture"] | CPU architecture (e.g., amd64, arm64, multi) |
| Refs | spec.extra_refs | Array of repo references (org, repo, base_ref) |
| Target | From spec.pod_spec.containers[0].args | The --target= value from ci-operator args |
| Variant | From spec.pod_spec.containers[0].args | The --variant= value from ci-operator args |
| RELEASE_IMAGE_LATEST | From spec.pod_spec.containers[0].env | The release image the job upgrades to or installs |
| RELEASE_IMAGE_INITIAL | From spec.pod_spec.containers[0].env | The initial release image (for upgrade jobs) |
Show full SKILL.md (317 more words)Show less
Notes on Release Annotations
release.openshift.io/tag: Present on release-controller-triggered jobs. Identifies the payload being validated. For upgrade jobs, this is the version the cluster upgrades to.release.openshift.io/from-tag: Only present on upgrade jobs. Identifies the version the cluster starts at before the upgrade. If absent, the job is not an upgrade job.- These annotations may not be present on manually triggered or presubmit jobs.
- The
RELEASE_IMAGE_LATESTandRELEASE_IMAGE_INITIALenvironment variables correspond to these tags and contain the full registry pull spec.
Error Handling
Case 1: Invalid Prow URL Format
If the URL doesn't match the expected pattern https://prow.ci.openshift.org/view/gs/...:
- Report the error to the user
- Show the expected URL format
Case 2: prowjob.json Not Found (404)
If the GCS web proxy returns a 404:
- The job may have been garbage collected or the URL may be incorrect
- Suggest verifying the Prow job URL is correct and the job exists
Case 3: Network Error
If the GCS web proxy is unreachable:
- Check connectivity to
gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com - The proxy does not require VPN or authentication
Examples
Example 1: Fetch a Periodic Upgrade Job
Input:
https://prow.ci.openshift.org/view/gs/test-platform-results-public/logs/periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-upgrade/2019864414127132672Key output fields:
Job Name: periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn-upgrade
Job Type: periodic
Build ID: 2019864414127132672
State: failure
Start Time: 2026-02-06T20:02:58Z
Completion Time: 2026-02-07T00:36:09Z
Cluster: build02
Payload Tag: 4.22.0-0.ci-2026-02-06-195709
Upgrade From Tag: 4.22.0-0.ci-2026-02-05-195709
Architecture: amd64
Target: e2e-gcp-ovn-upgrade
Variant: ci-4.22
RELEASE_IMAGE_LATEST: registry.ci.openshift.org/ocp/release:4.22.0-0.ci-2026-02-06-195709
RELEASE_IMAGE_INITIAL:registry.ci.openshift.org/ocp/release:4.22.0-0.ci-2026-02-05-195709Example 2: Non-Upgrade Job (No from-tag)
For a non-upgrade job, the Upgrade From Tag field will be absent:
Job Name: periodic-ci-openshift-release-master-ci-4.22-e2e-gcp-ovn
Job Type: periodic
Build ID: 2019864414127132999
State: success
Payload Tag: 4.22.0-0.ci-2026-02-06-195709
Upgrade From Tag: (not present - not an upgrade job)
Architecture: amd64
Target: e2e-gcp-ovn
Variant: ci-4.22Notes
- The
prowjob.jsonis uploaded to GCS by Prow's sidecar after the job completes (or is aborted). It may not be available for jobs still in progress. - The
managedFieldssection of the metadata can be omitted from output as it contains only field ownership bookkeeping. - The
metadata.labelssection is truncated for some fields (e.g., job name) due to Kubernetes label length limits. Always usemetadata.annotationsorspec.jobfor the full job name. - The GCS web proxy at
gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.comserves raw file content without authentication. - Duration can be calculated from
completionTime - startTime. - The
spec.decoration_config.timeoutfield shows the maximum allowed runtime for the job.
See Also
- Related Skill:
ci:prow-job-analysis(comprehensive Prow CI job failure analysis — test, install, disruption, and more)
© 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/ci/skills/fetch-prowjob-json of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Compare with similar skills
Fetch Prowjob JSON 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 Prowjob JSON this skillopenshift-eng/ai-helpers | 120 | — | ~2.1k | 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 repos | ~1.2k | Automated safety check: Notes | MIT | |
| Python Background Jobswshobson/agents | 40k | — | ~1.8k | Automated safety check: Pass | MIT | |
| 9Router Web Fetchdecolua/9router | 30k | — | ~941 | Automated safety check: Pass | MIT | |
| LobeHub Data Fetching Layerslobehub/lobehub | 83k | — | ~1.7k | 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.
Python Background Jobs
wshobson/agents
Python background job patterns including task queues, workers, and event-driven architecture.
9Router Web Fetch
decolua/9router
Fetches a web page through a 9Router server's web fetch endpoint and returns it as markdown, plain text or HTML, using one of several extraction providers.
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 Prowjob JSON
What does Fetch Prowjob JSON do?
Fetch and return key data from a Prow job's prowjob.json artifact given a Prow job URL. Fetch Prowjob JSON is an agent skill from openshift-eng/ai-helpers.
How do I install Fetch Prowjob JSON in Claude Code?
Run `npx skills add openshift-eng/ai-helpers --skill fetch-prowjob-json -a claude-code`. Or copy the skill folder (plugins/ci/skills/fetch-prowjob-json in openshift-eng/ai-helpers) into .claude/skills/fetch-prowjob-json in your project. Claude Code loads it when a task matches its description.
How do I install Fetch Prowjob JSON in Codex?
Run `npx skills add openshift-eng/ai-helpers --skill fetch-prowjob-json -a codex`. Or copy the skill folder (plugins/ci/skills/fetch-prowjob-json in openshift-eng/ai-helpers) into .agents/skills/fetch-prowjob-json in your project. Codex loads it when a task matches its description.
Can I use Fetch Prowjob JSON 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-prowjob-json -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-prowjob-json, .gemini/skills/fetch-prowjob-json, .github/skills/fetch-prowjob-json and .opencode/skills/fetch-prowjob-json in your project.
What does Fetch Prowjob JSON need to run?
Going by SKILL.md and its folder, Fetch Prowjob JSON needs the command-line tools its instructions call (curl).
Does Fetch Prowjob JSON access the network?
SKILL.md names 2 domains. In commands or code: gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com and prow.ci.openshift.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Fetch Prowjob JSON 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 Prowjob JSON use?
Fetch Prowjob JSON 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 Prowjob JSON use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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 Prowjob JSON?
Skills that share tags, products or a category with Fetch Prowjob JSON: Technical Job Search (github/awesome-copilot, 40k stars), Job Application Assistant (MadsLorentzen/ai-job-search, 45k stars), Python Background Jobs (wshobson/agents, 40k stars) and 9Router Web Fetch (decolua/9router, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fetch Prowjob JSON?
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.