rhecosystemappeng/rh-sre

**CRITICAL**: Use for ALL CVE discovery and listing. DO NOT call get_cves directly. Use when: "show critical CVEs", "CVEs on hostname X", "remediatable vulnerabilities", "impact of CVE-X", risk assessment. NOT for remediation (use /remediation). System-level: FIRST reply = pagination prompt (Step -1). Parsing: scripts/01-cve-response-parser.py.

**CRITICAL**: This skill must be used for CVE validation queries. DO NOT use raw MCP tools like get_cve directly. Validate CVE identifiers and check remediation availability in Red Hat Lightspeed. Use when: - "Is CVE-2024-1234 valid and remediable?" - "Check if CVE-X has automated remediation available" - "Verify these CVEs before creating a playbook" - "Validate CVE list for batch remediation" **DO NOT use this skill when** user requests full remediation - use /remediation skill instead: - "Create a remediation playbook for CVE-X" → /remediation skill - "Create playbook and execute it" → /remediation skill - "Remediate CVE-X" / "Patch CVE-X" → /remediation skill This skill orchestrates MCP tools (get_cve) for CVE validation. The /remediation skill invokes this skill as Step 2 of its workflow.

Generates a concise report of agents, skills, tools, and documentation accessed during a workflow for audit and learning purposes. Use when: - "Generate execution summary" - "Create execution report" - "Summarize what was used" - "Show execution summary" - "What agents/skills/tools were used?"

Query and display Red Hat Lightspeed managed system inventory. This skill focuses on discovery and listing only - for remediation actions, transition to the /remediation skill. Use when: - "Show the managed fleet" - "List all systems registered in Lightspeed" - "What systems are affected by CVE-X?" - "How many RHEL 8 systems do we have?" - "Show me production systems" **When NOT to use this skill** (use /remediation skill instead): - "Remediate CVE-X on these systems" - "Create a playbook for..." - "Patch system Y" This skill orchestrates MCP tools from lightspeed-mcp for fleet visibility and system inventory management.

Create AAP (Ansible Automation Platform) job templates for executing playbooks. Use when users request: - "Create a job template for this playbook" - "Set up a template to run remediation playbooks" - "Configure AAP to execute this playbook" - "Add a new job template for CVE remediation" This skill guides through adding playbooks to Git projects and creating job templates via AAP Web UI.

Verify an AAP job template meets requirements for executing CVE remediation playbooks. Use when: - "Does this job template support remediation playbooks?" - "Validate job template X for CVE remediation" - "Check if template is ready for playbook-executor" - Before playbook-executor selects a template NOT for: AAP MCP connectivity (use /mcp-aap-validator), creating templates (use /job-template-creator).

Validate AAP (Ansible Automation Platform) MCP server connectivity. Use when the user asks to "validate AAP MCP", "check AAP connection", or when other skills need to verify AAP MCP availability before job management or inventory operations.

Validate Red Hat Lightspeed MCP server connectivity. Use when the user asks to "validate Lightspeed MCP", "check Lightspeed connection", or when other skills need to verify lightspeed-mcp availability before CVE operations.

**CRITICAL**: Use for Ansible playbook execution via AAP. DO NOT call AAP MCP tools directly. Execute remediation playbooks with job management, dry-run, and reporting. Use after playbook-generator. Use when: - "Execute the remediation playbook" - "Launch the playbook on AAP" - "Run the CVE remediation job" - "Dry-run the playbook first" **Git Flow**: If template playbook path ≠ generated playbook, perform Git Flow (commit, push, sync) BEFORE launch.

**CRITICAL**: This skill ONLY GENERATES playbooks. It does NOT EXECUTE them. For execution, use /playbook-executor skill. Generate production-ready Ansible remediation playbooks for CVE vulnerabilities with Red Hat best practices, error handling, and Kubernetes safety patterns. Use when: - "Generate a remediation playbook for CVE-X" - "Create playbook for these CVEs" - "Get remediation playbook from Lightspeed" This skill calls the MCP tool (remediations__create_vuln_playbook) and returns the playbook **AS IS**. Do NOT modify, enhance, or add to the generated playbook. Any change requires explicit user validation first. **IMPORTANT**: - ALWAYS use this skill instead of calling create_vulnerability_playbook directly - NEVER execute playbooks using ansible-playbook CLI - ALWAYS delegate execution to /playbook-executor skill

**CRITICAL**: Use this skill for ALL CVE remediation workflows. DO NOT use individual skills piecemeal for end-to-end remediation. Use when users request: - CVE remediation playbooks or security patch deployment - Multi-step remediation (validation → context → playbook → execution) - Batch remediation across multiple systems or CVEs - End-to-end CVE management (analysis + remediation + verification) - Prioritizing and remediating CVEs (not just listing them) - Emergency security response with immediate remediation plans DO NOT use for simple queries: - "List critical CVEs" → Use /cve-impact skill - "What's the CVSS score for CVE-X?" → Use /cve-impact or /cve-validation - Standalone impact analysis without remediation → Use /cve-impact This skill orchestrates 6 specialized skills (cve-impact, cve-validation, system-context, playbook-generator, playbook-executor, remediation-verifier) for complete remediation workflows.

**CRITICAL**: This skill must be used for remediation verification. DO NOT use raw MCP tools like get_cve or get_host_details directly for verification. Verify CVE remediation success by checking Red Hat Lightspeed CVE status, validating package versions, and confirming service health. Use when: - "Verify CVE remediation was successful" - "Confirm package updates were applied" - "Check if CVE-X is fixed on target systems" - "Validate remediation after playbook execution" This skill orchestrates MCP tools (get_cve, get_cve_systems, get_host_details) for remediation verification. **IMPORTANT**: ALWAYS use this skill instead of calling verification MCP tools directly.

**CRITICAL**: This skill must be used for system inventory and context gathering. DO NOT use raw MCP tools like get_cve_systems or get_host_details directly. Gather system inventory and deployment context for CVE-affected systems, including RHEL version detection, environment classification, and deployment analysis. Use when: - "What systems are affected by CVE-X?" - "Gather system context for remediation planning" - "Analyze deployment architecture for CVE" - "Detect RHEL versions across affected systems" This skill orchestrates MCP tools (get_cve_systems, get_host_details) for system analysis. **IMPORTANT**: ALWAYS use this skill instead of calling get_cve_systems or get_host_details directly for system context gathering.