Catalog
github/centos-linux-triage

github

centos-linux-triage

Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.

v1.0Latest
New~227Updated Jun 26, 2026

CentOS Linux Triage

You are a CentOS Linux expert. Diagnose and resolve the user’s issue with RHEL-compatible commands and practices.

Inputs

  • ${input:CentOSVersion} (optional)
  • ${input:ProblemSummary}
  • ${input:Constraints} (optional)

Instructions

  1. Confirm CentOS release (Stream vs. legacy) and environment assumptions.
  2. Provide triage steps using systemctl, journalctl, dnf/yum, and logs.
  3. Offer remediation steps with copy-paste-ready commands.
  4. Include verification commands after each major change.
  5. Address SELinux and firewalld considerations where relevant.
  6. Provide rollback or cleanup steps.

Output Format

  • Summary
  • Triage Steps (numbered)
  • Remediation Commands (code blocks)
  • Validation (code blocks)
  • Rollback/Cleanup
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

62/100

Grade

C

Adequate

Safety

68

Quality

58

Clarity

72

Completeness

48

Summary

This skill guides an agent to diagnose and resolve CentOS/RHEL system issues using standard administrative tools. It provides a structured triage framework for problem identification, remediation steps, and rollback procedures, with explicit consideration for SELinux and firewalld.

Detected Capabilities

shell executionsystem log accesspackage management queriesservice state inspectionSELinux policy inspectionfirewall rule inspection

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

centos service troubleshootrhel system triagefirewalld selinux debuglinux daemon diagnosissystemd error investigation

Risk Signals

WARNING

Skill provides no explicit guardrails on remediation scope; agent could run destructive commands (package removal, service disabling) without explicit user confirmation

Instructions section, steps 2–4
INFO

No documented constraints on privilege requirements; skill assumes root/sudo access without explicitly stating this prerequisite

Instructions section
INFO

Rollback/cleanup step is mentioned in output format but no concrete rollback patterns or recovery procedures are provided in instructions

Output Format section

Use Cases

  • Troubleshoot CentOS service failures and daemon issues
  • Debug system configuration problems on RHEL-compatible distributions
  • Diagnose and resolve firewall or SELinux policy conflicts
  • Investigate application errors through systemd logs and journalctl
  • Perform package management troubleshooting with dnf/yum

Quality Notes

  • Strength: Clear structured format (Summary, Triage, Remediation, Validation, Rollback) aids readability and ensures agent covers essential steps.
  • Strength: Explicit mention of SELinux and firewalld considerations signals awareness of RHEL ecosystem complexity.
  • Strength: Validation and rollback steps are documented as required outputs, promoting safe practices.
  • Weakness: Instructions lack concrete examples of triage commands (e.g., 'journalctl -xe' for service errors) — agent must infer RHEL-specific syntax.
  • Weakness: No guidance on when to escalate (hardware failure, filesystem corruption, data loss scenarios) vs. when remediation is safe.
  • Weakness: 'Rollback/cleanup' in output format is underdefined — no examples of rollback procedures or how to handle state changes.
  • Weakness: Input parameters lack detail — 'Constraints' is vague; should specify bounds on system modifications (filesystem, network, user accounts, etc.)
  • Weakness: No discussion of RHEL/CentOS versioning impact (7 vs. 8 vs. 9 vs. Stream) — tools and configurations vary significantly.
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/centos-linux-triage in your dev environment

Command Palette

Search for a command to run...