Verified:GitHub

system-context

Assemble system context for CVE remediation using MCP tools.

48|31|Updated Feb 2, 2026

Search Tags:#system-context #cve-remediation #infrastructure-analysis #rhel-detection #environment-classification #lightspeed-mcp #remediation-strategy

Ready to run

npx skills add https://github.com/RHEcosystemAppEng/agentic-collections --skill system-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-context
Source: https://github.com/RHEcosystemAppEng/agentic-collections/tree/main/rh-sre/skills/system-context
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-collections --skill system-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a reliable method to collect comprehensive system inventory and deployment context for CVE-affected systems, ensuring remediation planning uses accurate data and avoids ad-hoc inquiries.

Core Features & Use Cases

Orchestrates MCP tools (get_cve_systems, get_host_details) to assemble a complete system profile for CVE context gathering.
Classifies deployment environment (RHEL versions, infrastructure type, tags) to inform remediation stratification.
Produces structured output suitable for feeding into remediation playbooks and verification steps.

Quick Start

Invoke this skill with a CVE identifier to gather affected systems and detailed host information for remediation planning.

Frequently Asked Questions about system-context

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

FAQPage Schema

How do I gather system context for CVE remediation across mixed RHEL environments?▼

This skill gathers CVE remediation context by classifying deployment environments and assembling full system profiles across mixed infrastructure types. It identifies affected systems across KVM, bare metal, and VMs to inform remediation stratification and avoid ad-hoc data collection.

What is the best way to identify affected systems for a specific CVE identifier?▼

Invoking this skill with a CVE identifier triggers the get_cve_systems MCP tool to identify affected hosts. It retrieves detailed system information using get_host_details, producing structured context that feeds directly into your remediation strategy and validation workflows.

Does CVE remediation planning work across different RHEL versions and infrastructure types?▼

Yes, this skill supports CVE remediation across multiple RHEL versions and infrastructure types including KVM, bare metal, and VMs. It classifies deployment environments by version and infrastructure tags to stratify remediation strategies and ensure accurate host context.

How do I generate remediation playbooks from gathered host details?▼

To generate remediation playbooks from gathered host details, feed the structured output from this skill into a playbook generator. It assembles comprehensive system profiles and deployment context specifically formatted to guide remediation strategy and validation workflows.

Why do I need full system context before planning CVE remediation?▼

You need full system context before planning CVE remediation to ensure accurate data usage and avoid ad-hoc inquiries. Collecting comprehensive inventory across mixed environments prevents targeting errors and ensures your remediation strategy matches the actual deployment context of affected hosts.