CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cve-impact

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./rh-sre/skills/cve-impact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Weight 40%Scale 1-5

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

The body delivers excellent executable guidance for the discovery/parsing path and uses reference files appropriately for bulk content, but it is undermined by heavy duplication (HITL prompt twice, validation twice, tool lists three times), an ordering contradiction between the validation prerequisite and the HITL-first gate, and a reference graph where the mandatory consultation documents are empty pointer stubs while half the bundle is orphaned. Steps 6–7 are skeletal, leaving the back half of the workflow underspecified.

Suggestions

State the HITL pagination prompt and the MCP validation procedure once each and reference them from the other location; collapse the three tool listings (Prerequisites, Dependencies, Tools Reference) into a single table.

Resolve the ordering conflict: make Step -1 unambiguously first and reword the Prerequisites 'before executing any operations' claim to 'before any MCP tool call'.

Fix the reference graph: replace the pointer-stub files (cvss-scoring.md, insights/*) with real content or working links, and either reference or remove the orphaned ansible/, rhel/, and unreferenced root files.

Flesh out Steps 6 and 7 with the same concrete output formats and tool guidance used in Steps 2–5, since they currently consist of one line each.

DimensionReasoningScore

Conciseness

Mostly efficient — no explaining of concepts Claude already knows, bulk content delegated to reference files, tables used for flow routing — but the body repeats itself heavily: the full HITL pagination prompt appears verbatim twice (Step -1 and again inside Step 1), MCP validation instructions appear twice (Prerequisites and Step 0), tool listings appear three times (Prerequisites, Dependencies, Tools Reference), and the remediation relationship is explained twice. This is the 'mostly efficient but could be tightened' anchor; not 2 because the redundancy is duplication rather than padded explanation and the majority of sections earn their tokens.

3 / 5

Actionability

The main path is strongly concrete (executable SCRIPTS_DIR check, exact parser invocations with FILTER_REMEDIATABLE=1 and multi-file aggregation, copy-paste HITL prompts, parameter gotchas like 'use system_uuid, NOT system_id'), but key required details are missing: the four mandatory 'Document Consultation' steps in Steps 2–5 direct reading files that in the actual bundle are one-line pointer stubs (cvss-scoring.md contains only '../../cve-validation/references/cvss-scoring.md', insights/insights-api.md and insights/fleet-management.md likewise), and Steps 6 and 7 are single skeletal lines ('Analyze business impact...', 'Check if automated playbook...') with no method. That mix lands on anchor 3 ('concrete guidance but incomplete; missing key details'); not 4 because dead-end mandatory references and vestigial steps are more than minor gaps.

3 / 5

Workflow Clarity

Steps are numbered and sequenced with HITL gates, wait conditions, PASSED/PARTIAL/FAILED validation branching, and explicit anti-patterns — but the sequence contains a direct contradiction: the Prerequisites section says 'Before executing any operations, execute the /mcp-lightspeed-validator skill' while Step -1 mandates that the first reply be the pagination prompt and says 'Do not validate MCP... HITL comes first'. The HITL gate is also duplicated (Step -1 and inside Step 1), creating ambiguity about where gating actually occurs, and Steps 6–7 have no checkpoints. This fits anchor 3 ('steps listed but validation/sequence gaps'); not 4 because an ordering contradiction is more than a minor gap.

3 / 5

Progressive Disclosure

Structure is genuinely good — flows split into three reference files, separate parsing guide, output templates, examples, and error handling, plus a Reference Files table — but scored against the actual bundle the reference graph is broken: five referenced files (cvss-scoring.md, skill-invocation.md, insights/insights-api.md, insights/fleet-management.md, insights/vulnerability-logic.md) are single-line pointer stubs to sibling skills that do not exist in this bundle, effectively creating dead two-hop references, and ten-plus bundle files (ansible/*, rhel/*, README.md, SOURCES.md, lightspeed-mcp-parameters.md, 01-parameter-reference.md, compliance-frameworks.md) are never referenced from SKILL.md at all. Anchor 3 fits ('could be better organized... content that should be separate'); not 4 because broken mandatory references and orphaned directories are more than minor organization gaps.

3 / 5

Total

12

/

20

Passed

Description

73%Weight 40%Scale 1-5

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

The description is trigger-focused and routing-oriented: it excels at distinctiveness with an explicit NOT-for boundary and natural trigger phrases, and it includes an explicit 'Use when' clause. Its weakness is the thin 'what' — it captures discovery/listing but undersells the impact-analysis, systems-identification, and risk-assessment capabilities the skill actually performs.

Suggestions

Add one sentence enumerating the concrete capabilities, e.g. 'Analyzes CVE impact: retrieves CVE metadata, identifies affected systems, classifies by environment, and produces risk assessments.'

Broaden trigger coverage with common synonyms such as 'vulnerabilities on my systems', 'affected systems', and 'CVE details'.

State the what/when pairing in third-person declarative form ('Analyzes CVE impact... Use when...') rather than leading with the '**CRITICAL**' directive, so the capability description comes before model-facing instructions.

DimensionReasoningScore

Specificity

Phrases like 'Use for ALL CVE discovery and listing' and 'Parsing: scripts/01-cve-response-parser.py' name the domain plus a couple of concrete actions, but the description never states the skill's core capabilities (identify affected systems, classify environments, produce risk assessments) that the body documents. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); not 4 because several specific actions are missing, not 2 because it goes beyond a bare domain label with concrete routing behavior.

3 / 5

Completeness

An explicit 'Use when:' clause with concrete trigger phrases answers 'when', and 'Use for ALL CVE discovery and listing' plus the 'NOT for remediation' boundary answer 'what' — both are present. Not 5 because the 'what' side is thin: it describes discovery/listing but omits the impact-analysis and risk-assessment capabilities that the body presents as the skill's purpose; not 3 because neither side is missing or merely implied.

4 / 5

Trigger Term Quality

Triggers 'show critical CVEs', 'CVEs on hostname X', 'remediatable vulnerabilities', 'impact of CVE-X', 'risk assessment' are natural user phrasings with good variety across query types. Not 5 because common synonyms like 'vulnerabilities on system', 'affected systems', or 'CVE details' are absent; not 3 because the coverage of natural phrasings is genuinely good rather than partial.

4 / 5

Distinctiveness Conflict Risk

'Use for ALL CVE discovery and listing' carves out a clear niche, and 'NOT for remediation (use /remediation)' explicitly excludes the nearest competing skill. Triggers are CVE-specific enough that mis-triggering risk is minimal, matching the anchor-5 example of a clear niche with distinct triggers.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 6 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 6 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-sre/skills/cve-impact/SKILL.md

Reviewed

Table of Contents

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.