remediation-verifier

Validate CVE remediation by checking Lightspeed vulnerability status, updated packages, and service health.

48|31|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/RHEcosystemAppEng/agentic-collections --skill remediation-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remediation-verifier
Source: https://github.com/RHEcosystemAppEng/agentic-collections/tree/main/rh-sre/skills/remediation-verifier
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-collections --skill remediation-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CVE remediation can be hard to trust without verification; this skill provides automated end-to-end confirmation by checking vulnerability status, installed packages, and service health after remediation.

Core Features & Use Cases

  • Verifies CVE remediation status by querying Lightspeed for CVE records and affected systems.
  • Validates that target hosts have updated packages to fixed versions and that critical services are running normally.
  • Use after remediation playbooks or for stand-alone verification in ongoing vulnerability management workflows, with integration guidance for the sre-agents:remediator agent.

Quick Start

After remediation, run the verification against the targeted systems to obtain a consolidated report and confirmation of CVE resolution.

Frequently Asked Questions about remediation-verifier

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

FAQPage Schema
How do I verify CVE remediation was successful across targeted systems?

Verify CVE remediation by querying Lightspeed vulnerability status, checking installed packages for updated versions, and confirming critical services are running normally across targeted hosts to produce a structured verification result.

What does CVE remediation verification check beyond vulnerability status?

CVE remediation verification validates updated package versions on target hosts and confirms that critical services are running normally, providing end-to-end confirmation that the vulnerability resolution is fully effective.

Can I run standalone verification in ongoing vulnerability management workflows?

Yes, you can run standalone verification in ongoing vulnerability management workflows to check CVE remediation status, or apply it after remediation playbooks to confirm vulnerability resolution across systems.

How does remediation verification integrate with the sre-agents:remediator agent?

Remediation verification integrates with the sre-agents:remediator agent by using MCP tools including get_cve, get_cve_systems, and get_host_details to query Lightspeed records and produce a structured confirmation of CVE resolution.

What is the best way to confirm CVE resolution after running remediation playbooks?

The best way to confirm CVE resolution after remediation playbooks is to run automated verification that queries Lightspeed for CVE records, validates fixed package versions, and checks service health to generate a consolidated report.

Why does CVE remediation require automated verification across systems?

CVE remediation requires automated verification because manual checks are hard to trust; automated end-to-end confirmation validates vulnerability status, installed package updates, and service health across targeted systems reliably.