remediation

**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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, clearly sequenced orchestration workflow with strong validation gates and human-in-the-loop checkpoints, but it is verbose with redundant confirmation sections and ships several dangling references to non-existent files.

Suggestions

Consolidate the confirmation/gate rules: state them once in the workflow steps and reference that from 'Critical: Human-in-the-Loop Requirements' and 'Important Reminders' instead of restating them — removes ~40 lines of repetition.

Fix or remove the dangling references that are not in the bundle: docs/references/skill-invocation.md, docs/references/lightspeed-mcp-tool-failures.md, docs/ansible/cve-remediation-templates.md, and docs/rhel/package-management.md.

Repair references/01-remediation-indicators.md — it currently contains the literal text '../../cve-validation/references/01-remediation-indicators.md' rather than the remediation-indicator content it is cited to support.

Dimension	Reasoning	Score
Conciseness	The content is mostly actionable rather than explanatory, but the same confirmation/gate rules are restated across the Workflow steps, 'Critical: Human-in-the-Loop Requirements', and 'Important Reminders' sections, and the When-to-Use block repeats the frontmatter — it could be tightened.	2 / 3
Actionability	Provides concrete invoke prompts per step, exact gate logic (remediatable → proceed; else explain/offer/continue), explicit tool rules (use the Skill tool, not 'Task Output'; absolute Git Flow path), and specific expected outputs — copy-ready guidance for an instruction-only skill.	3 / 3
Workflow Clarity	Seven explicitly sequenced steps with mandatory ordering ('Do NOT proceed to Step 1 until Step 0 is complete'), validation checkpoints (PASSED/FAILED/PARTIAL, the remediatable gate), user-confirmation gates, and a checklist-format remediation plan — clear sequencing with feedback loops for destructive/batch operations.	3 / 3
Progressive Disclosure	Sections are well-organized and references are one-level-deep and inline-signaled, but four referenced paths (docs/references/skill-invocation.md, docs/references/lightspeed-mcp-tool-failures.md, docs/ansible/cve-remediation-templates.md, docs/rhel/package-management.md) do not exist in the bundle and references/01-remediation-indicators.md is a broken pointer file.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states what the skill does, when to use it, and when not to, with explicit redirects to sibling skills that prevent mis-selection.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'CVE remediation playbooks or security patch deployment', 'Multi-step remediation (validation → context → playbook → execution)', 'End-to-end CVE management (analysis + remediation + verification)' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('orchestrates 6 specialized skills ... for complete remediation workflows') and when (a 'Use when users request:' bullet list plus an explicit 'DO NOT use for simple queries' boundary).	3 / 3
Trigger Term Quality	Covers natural terms users would say — 'CVE remediation playbooks', 'security patch deployment', 'batch remediation', 'emergency security response with immediate remediation plans' — with good variation rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The 'DO NOT use for simple queries' block redirects each simple case to a sibling skill (/cve-impact, /cve-validation), carving a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 6 missing, 6 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: RHEcosystemAppEng/agentic-collections
Path: rh-sre/skills/remediation/SKILL.md
Commit: e47237b

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.