System Configuration Analysis

Analyze sosreport archives to diagnose configuration-related system issues.

112|305|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill system-configuration-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: System Configuration Analysis
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/sosreport/skills/system-config-analysis
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill system-configuration-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and diagnoses system configuration problems that cause service failures, security issues, and performance degradation by analyzing sosreport archives.

Core Features & Use Cases

  • Comprehensive System Analysis: Extract and analyze OS details, installed packages, service status, and security policies from sosreport data.
  • Service Failure Diagnosis: Pinpoint the root causes of failed systemd services and application services.
  • Use Case: When a web server fails to start, use this Skill to analyze the sosreport and discover that port 80 is already in use by another process.

Quick Start

Analyze the system configuration from the extracted sosreport directory located at /path/to/sosreport.

Frequently Asked Questions about System Configuration Analysis

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

FAQPage Schema
How do I diagnose system issues from a sosreport archive?

Diagnose system issues by analyzing sosreport archives to extract OS details, installed packages, service status, and security policies. The Skill parses configuration files, kernel parameters, and systemd data to identify root causes of service failures, misconfigurations, and security problems across the system.

Can I use sosreport analysis to troubleshoot failed services?

Yes. Analyze systemd service failures by examining service status data, configuration files, and system state captured in sosreport. The Skill identifies root causes like port conflicts, missing dependencies, or misconfigured SELinux policies that prevent services from starting.

What system configuration details can I extract from sosreport?

Extract OS release info, kernel version, uptime, installed RPM/DEB packages, systemd service status, SELinux/AppArmor policies, sysctl parameters, and resource limits. The Skill parses /etc, /proc, and systemctl output to build a comprehensive diagnostic view of system configuration.

How does SELinux policy evaluation help identify configuration problems?

SELinux policy analysis reveals security constraint violations that block services or applications. The Skill evaluates policy details and enforced rules from sosreport to diagnose why processes fail due to permission denials or policy misconfigurations.

Do I need to extract sosreport before analysis, or can I work with the archive directly?

Extract the sosreport archive first. The Skill analyzes the sosreport directory structure containing organized system data files, configuration snapshots, and systemctl output needed to perform comprehensive diagnostic analysis.

What's the difference between analyzing sosreport and live system inspection?

Sosreport analysis examines a point-in-time system snapshot captured in an archive, enabling diagnosis without live system access and allowing offline troubleshooting. This approach preserves historical state and is ideal for remote systems or post-incident analysis.