agentmods.dev

Prow Job Analyze Install Failure

Prow Job Analyze Install Failure is a skill for Claude Code, Codex from wangke19/gemini-ai-helpers. It costs 49 tokens per session (7,955 once invoked), scanned A, original, Apache-2.0.

A guide for diagnosing failed OpenShift installations in Prow, OpenShift’s continuous-integration system. It examines installer logs, collected log bundles, and system reports from failed jobs.

In plain words
What is it for?
Investigating Prow jobs whose installation tests fail, using the job URL and stored failure logs.
Why use it?
It organizes the evidence needed to find whether an installation failed during bootstrap, cluster creation, or another stage.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 2repo 5mo ago A scan 49 tokens original Apache-2.0

Good fit Investigating Prow jobs whose installation tests fail, using the job URL and stored failure logs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure
View source ↗ wangke19/gemini-ai-helpers
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wangke19/gemini-ai-helpers --skill prow-job-analyze-install-failure
Clone the repo
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Prow Job Analyze Install Failure

README.md
[![agentmods](https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure/github.svg)](https://agentmods.dev/skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure)
Your own site
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Prow Job Analyze Install Failure

Your own site · 80×15
<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/prow-job-analyze-install-failure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,955 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.07955
Opus 5 $0.00024 $0.03978
Sonnet 5 $0.00010 $0.01591
Haiku 4.5 $0.00005 $0.00796

Measured 12d ago against content hash 2dbeeb0a9f31, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

Prow Job Analyze Install Failure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

extensions/ci/skills/prow-job-analyze-install-failure/SKILL.md · 696 lines

How it starts

The opening of the file, as written. The whole thing — 696 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prow Job Analyze Install Failure

This skill helps debug OpenShift installation failures in CI jobs by downloading and analyzing installer logs, log bundles, and sosreports from Google Cloud Storage.

When to Use This Skill

Use this skill when:

  • A CI job fails with "install should succeed" test failure
  • You need to debug installation failures at specific stages (bootstrap, install-complete, etc.)
  • You need to analyze installer logs and log bundles from failed CI jobs

Prerequisites

Before starting, verify these prerequisites:

  1. gcloud CLI Installation

  2. gcloud Authentication (Optional)

    • The test-platform-results bucket is publicly accessible
    • No authentication is required for read access
    • Skip authentication checks

Input Format

The user will provide:

  1. Prow job URL - URL to the failed CI job
    • Example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview/1983307151598161920
    • The URL should contain test-platform-results/

Understanding Job Types from Names

Job names contain important clues about the test environment and what to look for:

  1. Upgrade Jobs (names containing "upgrade")
    • These jobs perform a fresh installation first, then upgrade
    • Minor upgrade jobs: Contain "upgrade-from-stable-4.X" in the name - upgrade from previous minor version (e.g., 4.21 job installs 4.20, then upgrades to 4.21)
      • Example: periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-gcp-ovn-rt-upgrade
    • Micro upgrade jobs: Have "upgrade" in the name but NO "upgrade-from-stable" - upgrade within the same minor version (e.g., earlier 4.21 to newer 4.21)
      • Example: periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips
      • Example: periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade
    • If installation fails, the upgrade never happens
    • Key point: Installation failures in upgrade jobs are still installation failures, not upgrade failures

Read the full file on GitHub · 696 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 696 lines · 49 tokens per session scan A 2dbeeb0a9f31

Subscribe to this mod's changes

Prow Job Analyze Install Failure is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 7,955 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

CI and CDDebuggingDevOps and cloudextentionsgemini-cliopenshiftredhat
Related

Other skills, from other repositories

ci-fix-with-memory

Automatically invoke when CI checks fail on a PR. Triggers on: any mention of CI failure, red checks, failed GitHub Actions, or "CI is broken/failing". Reads session handoffs and a known-issues log to avoid repeating failed fix attempts. Do NOT wait for user to ask — invoke as soon as a CI failure is confirmed. Not…

jerseycheese/agent-skills · 101 tokens

gh-fix-ci

Use when a user asks to debug or fix failing GitHub PR checks / GitHub Actions runs (e.g., 'CI is red', 'why is this PR failing', 'fix the failing checks', 'PR checks broken'). Inspects checks via gh, summarizes failure context, and implements when the user has asked for a fix.

dinglebear-ai/dendrite · 72 tokens

fix-ci

Diagnose and fix CI failures using GitHub Actions logs. Iterates through diagnose-fix-verify cycles until CI passes (max 3 iterations).

thoreinstein/beads-workflow · 33 tokens

temps-plugin

Build external plugins for the Temps deployment platform. Use when the user wants to create, modify, or debug a Temps plugin binary — a standalone Rust process that communicates with Temps over a Unix domain socket. Also use when the user mentions "temps plugin", "external plugin", "plugin binary", "plugin for temps"…

gotempsh/temps · 120 tokens

spk-admin-setup-doctor

Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.

Priivacy-ai/spec-kitty · 31 tokens

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens