Understanding Konflux Resources
Use when user asks about Konflux resources, Custom Resources, Applications, Components, Snapshots, IntegrationTestScenarios, ReleasePlans, ReleasePlanAdmissions, or namespace placement. Provides quick reference for what Konflux resources are, who creates them, and where they belong (tenant vs managed namespace).
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 understanding-konflux-resourcesgit clone --depth 1 https://github.com/konflux-ci/agent-plugins.git /tmp/agent-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/agent-plugins/skills/understanding-konflux-resources ~/.claude/skills/understanding-konflux-resourcesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Understanding Konflux Resources ## Overview Konflux uses Kubernetes Custom Resources (CRs) to manage CI/CD workflows. Understanding which resource to use, who creates it, and where it belongs prevents common configuration errors. **Core principle:** Some resources YOU create, others Konflux creates automatically. Knowing the difference prevents manual work that's already automated. **NAMING CONVENTION - CRITICAL:** Always write resource names WITHOUT spaces: ReleasePlan, ReleasePlanAdmission, IntegrationTestScenario NEVER use spaces: ~~"Release Plan"~~, ~~"Release Plan Admission"~~, ~~"Integration Test Scenario"~~ **⚠️ COMMON HALLUCINATION - MUST CORRECT:** ReleasePlanAdmission (RPA) is **NOT** automatically created by Konflux. ReleasePlanAdmission (RPA) is **NOT** auto-generated by the release service. ReleasePlanAdmission (RPA) **IS** manually created by a Platform Engineer in the managed namespace. **WHO CREATES WHAT - Critical Facts:** - **ReleasePlanAdmission (RPA)**: Platform Engineer creates in managed namespace (NOT you, NOT auto-created) - **Snapshot**: Auto-created by Integration Service (NOT you) - **ReleasePlan (RP)**: You create in tenant namespace - **IntegrationTestScenario (ITS)**: You create in tenant namespace **NAMESPACE PLACEMENT - Critical for RP/RPA:** - **ReleasePlan (RP)**: Goes in tenant namespace (your workspace) - **ReleasePlanAdmission (RPA)**: Goes in managed namespace (platform team controlled)
Details
- Skill name
understanding-konflux-resources- Repository
- konflux-ci/agent-plugins
- Path
skills/understanding-konflux-resources/SKILL.md- License
- Apache-2.0
- Repo updated
- 3 November 2026
FAQ
What does the Understanding Konflux Resources skill do?
Use when user asks about Konflux resources, Custom Resources, Applications, Components, Snapshots, IntegrationTestScenarios, ReleasePlans, ReleasePlanAdmissions, or namespace placement. Provides quick reference for what Konflux resources are, who creates them, and where they belong (tenant vs managed namespace).
How do I install the Understanding Konflux Resources 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 Understanding Konflux Resources 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 Failed Plrs
9konflux-ci/agent-plugins
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.
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.
Design Fidelity Verify
6jeltehomminga/figma-design-skills
Prove a running app matches its design spec by measuring rendered values, not eyeballing a screenshot. Use when the user says "verify the design", "is this pixel-perfect", "check against Figma", "does the app match the design", or "design QA this screen". Runs a bounded vision+numeric loop over web or mobile, classifying every spec row rather than reporting a bare pixel delta. Consumes the figma-design-extract spec table.
Red Hat Konflux Teams
9konflux-ci/agent-plugins
Use when needing to know which Red Hat team owns a Konflux-related repository (konflux-ci, hermetoproject, conforma orgs), which JIRA project or component to file issues against, or how the Red Hat Konflux engineering organization maps to the codebase.
Figma Design Extract
6jeltehomminga/figma-design-skills
Extract exact design values from a Figma node into a build-ready spec table, instead of eyeballing a screenshot. Use when the user shares a figma.com node URL, or says "implement this Figma design", "build this component from Figma", "extract the Figma values", or "match the Figma". This is design-to-code only - to push code into Figma, use figma-generate-design instead.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.