List Components

Fetch deduplicated, sorted component names from the Sippy API for an OpenShift release.

112|305|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill list-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: List Components
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/component-health/skills/list-components
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill list-components

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual effort of discovering and validating which components are tracked in the Sippy component readiness system for any OpenShift release.

Core Features & Use Cases

  • Component Discovery: Fetch a complete, alphabetically sorted list of all components for a specific release.
  • Name Validation: Verify component names exist before querying regression or bug data.
  • Use Case: When preparing a comprehensive analysis of OpenShift 4.21 component health, use this Skill to get all 42 tracked components, then iterate through each one for detailed regression analysis.

Quick Start

Use the List Components skill to fetch all component names for OpenShift release 4.21.

Frequently Asked Questions about List Components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover all components tracked for an OpenShift release?

Component discovery fetches a complete, alphabetically sorted list of all components tracked in Sippy for a specific OpenShift release. The Skill queries the Sippy API with a release parameter (formatted as release-main) and returns a deduplicated JSON object containing the component count and full component list.

Can I validate component names before querying OpenShift regression data?

Yes. Name validation checks whether component names exist in Sippy's tracked inventory for your target release before you use them in regression or bug queries. This prevents failed queries and supports autosuggestion workflows.

What are the requirements to fetch component lists from Sippy?

Requirements include Python 3, network access to the Sippy API endpoint, and knowledge of the OpenShift release version you're querying. The Skill constructs the view parameter automatically as release-main and outputs JSON containing release, view, component_count, and components.

How do I use component lists for OpenShift health analysis workflows?

Fetch the complete component list for your target release, then iterate through each component name to gather detailed regression analysis or health metrics. This enables comprehensive reports across all tracked components without manual discovery.

What does the Skill output after fetching components?

The Skill emits a JSON object containing the release version, view identifier, total component count, and a deduplicated, alphabetically sorted array of all component names for that release.