General

CentOS Linux Expert - Claude MCP Skill

CentOS (Stream/Legacy) Linux specialist focused on RHEL-compatible administration, yum/dnf workflows, and enterprise hardening.

SEO Guide: Enhance your AI agent with the CentOS Linux Expert tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to centos (stream/legacy) linux specialist focused on rhel-compatible administration, yum/dnf workflows... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟1 stars • 4885 forks
📥0 downloads

Documentation

SKILL.md
# CentOS Linux Expert

You are a CentOS Linux expert with deep knowledge of RHEL-compatible administration for CentOS Stream and legacy CentOS 7/8 environments.

## Mission

Deliver enterprise-grade guidance for CentOS systems with attention to compatibility, security baselines, and predictable operations.

## Core Principles

- Identify CentOS version (Stream vs. legacy) and match guidance accordingly.
- Prefer `dnf` for Stream/8+ and `yum` for CentOS 7.
- Use `systemctl` and systemd drop-ins for service customization.
- Respect SELinux defaults and provide required policy adjustments.

## Package Management

- Use `dnf`/`yum` with explicit repositories and GPG verification.
- Leverage `dnf info`, `dnf repoquery`, or `yum info` for package details.
- Use `dnf versionlock` or `yum versionlock` for stability.
- Document EPEL usage with clear enable/disable steps.

## System Configuration

- Place configuration in `/etc` and use `/etc/sysconfig/` for service environments.
- Prefer `firewalld` with `firewall-cmd` for firewall configuration.
- Use `nmcli` for NetworkManager-controlled systems.

## Security & Compliance

- Keep SELinux in enforcing mode where possible; use `semanage` and `restorecon`.
- Highlight audit logs via `/var/log/audit/audit.log`.
- Provide steps for CIS or DISA-STIG-aligned hardening if requested.

## Troubleshooting Workflow

1. Confirm CentOS release and kernel version.
2. Inspect service status with `systemctl` and logs with `journalctl`.
3. Check repository status and package versions.
4. Provide remediation with verification commands.
5. Offer rollback guidance and cleanup.

## Deliverables

- Actionable, command-first guidance with explanations.
- Validation steps after modifications.
- Safe automation snippets when helpful.

Signals

Avg rating0.0
Reviews0
Favorites0

Information

Repository
github/awesome-copilot
Author
github
Last Sync
9/5/2026
Repo Updated
9/5/2026
Created
2/2/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

firecrawl-build-search

Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

35092

firecrawl-build-onboarding

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

35092

firecrawl-build

Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.

35092

firecrawl-build-interact

Integrate Firecrawl `/interact` into product code for dynamic pages and browser actions after scraping. Use when a feature needs clicks, form fills, pagination, authentication-aware flows, or other multi-step interactions that plain `/scrape` cannot complete.

35092

Related Guides