Investigating Failed Plrs
Use when you want to investigate why a specific Konflux PipelineRun failed. Drills through PLR conditions, failed TaskRuns, pod status, container exit codes, and timing. Use when user asks "why did my build fail?", "PLR failed", "pipeline error", or invokes /investigating-failed-plrs.
Install
/plugin marketplace add konflux-ci/agent-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add konflux-ci/agent-plugins --skill investigating-failed-plrsgit clone --depth 1 https://github.com/konflux-ci/agent-plugins.git /tmp/agent-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/agent-plugins/skills/investigating-failed-plrs ~/.claude/skills/investigating-failed-plrsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Investigate Failed Konflux PipelineRun Help user answer: "Why did my PipelineRun fail?" Work through these steps interactively — ask user for input when needed, skip steps where info already provided. ## Prerequisites - `oc` CLI with KubeArchive plugin installed - check this with `oc ka version` (if not, let user install using <https://kubearchive.github.io/kubearchive/main/cli/installation.html>) - `yq` and `jq` available - check with `yq --version` and `jq --version` - Logged into the target Konflux cluster (`oc whoami --show-server`) ## Step 1: Identify Cluster and Tenant Check currently logged-in cluster: ``` oc whoami --show-server ``` Ask user for the tenant namespace (`<something>-tenant`). Verify access: ``` oc get namespace/<tenant> ``` If you have a skill for listing available Konflux clusters, use it. Otherwise, ask the user which cluster to connect to. If login is needed, suggest: ``` oc login --web <api_server> ``` ## Step 2: Find the Failed PipelineRun **IMPORTANT**: KubeArchive wraps results in `.items[]` — always use `yq '.items[0]...'`. If user already provided a specific PipelineRun name, skip to Step 3. **Find recent failed ones:** ``` oc ka get -n <tenant> --limit 20 pipelinerun -o yaml | yq '.items[] | select(.status.conditions[0].status != "True") | [.metadata.name, .status.conditions[0].reason, .metadata.creationTimestamp] | @tsv' ``` If no failures found with the above, list all recent PLRs and let user pick:
Details
- Skill name
investigating-failed-plrs- Repository
- konflux-ci/agent-plugins
- Path
skills/investigating-failed-plrs/SKILL.md- License
- Apache-2.0
- Repo updated
- 3 November 2026
FAQ
What does the Investigating Failed Plrs skill do?
Use when you want to investigate why a specific Konflux PipelineRun failed. Drills through PLR conditions, failed TaskRuns, pod status, container exit codes, and timing. Use when user asks "why did my build fail?", "PLR failed", "pipeline error", or invokes /investigating-failed-plrs.
How do I install the Investigating Failed Plrs skill?
Claude Code plugin: /plugin marketplace add konflux-ci/agent-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Investigating Failed Plrs popular?
It lives in konflux-ci/agent-plugins, which has 9 GitHub stars and 18 forks.
Related skills
Component Build Status
9konflux-ci/agent-plugins
Use to trigger component builds, releases or get a component or application status
Investigating Slow Builds
9konflux-ci/agent-plugins
Use when you want to investigate why Konflux builds/pipeline runs are slow. Use when user asks "why are my builds slow?", "pipeline runs taking long", "slow PLR", or invokes /investigating-slow-builds.
Konflux Architecture
9konflux-ci/agent-plugins
Use when needing to understand Konflux architecture, design decisions, service responsibilities, APIs, build/test/release workflows, or how Konflux components fit together.
Deck Review
10Founders-Edge/toolkit
Check a startup pitch deck for the essentials and signals an early-stage investor looks for, before the founder sends it out. Use this skill whenever someone asks to review their deck, check if their pitch deck is ready, find what's missing from their deck, or asks whether their company is "investable" or "venture scale." Triggers on: "review my deck", "is my pitch deck ready", "check my pitch deck", "what's missing from my deck", "is my company investable", "are we venture scale", "would an investor fund this". This is a founder-facing essentials-and-investability check, tuned for US-based ve
Investor Update
10Founders-Edge/toolkit
Help a founder write a clear, regular update to their investors. Use this skill whenever someone asks to write or draft an investor update, a monthly or quarterly update, a backers/angels update, or asks for an investor-update template or cadence advice. Triggers on: "write an investor update", "monthly investor update", "draft an update for my investors", "quarterly update to backers", "investor update template", "what should go in my investor update". Produces a tight, skimmable update with the sections investors actually read — TL;DR, key metrics, highlights, lowlights, asks, and runway — i
Crypto Market Search
9coinpaprika/claude-marketplace
Search and analyze cryptocurrency market data using CoinPaprika. Activates when users search for coins, ask about prices, request market overviews, or look up tokens by contract address.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.