CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

red-hat-cve-explainer

Explain a CVE using Red Hat's severity rating system. Looks up the CVE, explains the rating, and suggests a course of action.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 is a tight, highly actionable runbook: concrete tool calls with parameters, explicit fallback chains, and a fully templated output with per-severity recommendations. Its only real flaws are the redundant Workflow section overlapping the Lookup Sequence and slightly imperfect section organization.

Suggestions

Merge the "Workflow" section into "Lookup Sequence" (or replace it with a one-line pointer) to remove the duplicated extraction and lookup steps.

Consider folding the opening instruction ("Extract CVE-YYYY-NNNNN... Handle multiple CVEs separately") into the lookup section so each step appears exactly once.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no filler about what a CVE is, and every section (advisory-type table, severity criteria, output template) earns its place. It misses a 5 because the "Workflow" section ("Extract CVE ID from the user message", "Look up CVE metadata", "Look up linked advisories") duplicates the more detailed "Lookup Sequence" section and the opening instruction, which could be trimmed.

4 / 5

Actionability

Fully executable guidance: exact tool invocations with parameter keys and values ("get_cve_by_id — cve_id: \"<CVE-ID>\""), concrete URLs ("https://access.redhat.com/security/cve/<CVE-ID>", the NVD fallback), a literal per-severity action script ("Patch immediately. Exploitable by remote unauthenticated attackers."), and edge cases covered (no Red Hat data, MCP unavailable, no advisory). This matches the copy-paste-ready anchor.

5 / 5

Workflow Clarity

The lookup sequences are explicitly ordered with stop conditions ("stop when you have data"), step-gating ("after step 1-2 succeeds"), and an error-recovery path at every fallback ("No Red Hat data: say so, direct to NVD"). The skill is read-only so the destructive/batch validation cap does not apply, and the output section covers the empty-advisory case, matching the explicit-validation/error-recovery anchor.

5 / 5

Progressive Disclosure

No bundle files exist and all content (severity definitions, advisory-type table, output template) is compact and appropriately inlined under clear headers, giving good structure and easy navigation. It sits at anchor 4 rather than 5 because of the minor organization gap of the redundant Workflow/Lookup Sequence sections, and the ~77-line body exceeds the 'under 50 lines' carve-out where well-organized sections alone warrant a 5.

4 / 5

Total

18

/

20

Passed

Description

66%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 concise, specific, and clearly third-person, with a well-defined Red Hat niche. Its main weakness is the complete absence of a 'when to use' trigger clause, which both caps completeness and leaves common trigger synonyms (CVSS, vulnerability, advisory, patch) uncovered.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about a CVE, its severity or CVSS score, or whether/when to patch, especially in Red Hat environments."

Include natural synonyms users say, such as "vulnerability", "CVSS", "RHSA/advisory", and "patch", alongside "CVE" and "severity".

Mention what the explanation covers (severity rating, affected Red Hat products, fix/advisory status, recommended action) to close the specificity gap with the body's actual capabilities.

DimensionReasoningScore

Specificity

"Looks up the CVE, explains the rating, and suggests a course of action" names three concrete actions anchored to "Red Hat's severity rating system", matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because it omits capabilities the body delivers (affected products, advisory/RHSA details, patch status) and is well above 3's 1-2 action coverage.

4 / 5

Completeness

The 'what' is clear ("Explain a CVE using Red Hat's severity rating system. Looks up the CVE, explains the rating, and suggests a course of action") but there is no 'Use when...' clause or equivalent explicit trigger guidance. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"CVE", "Red Hat", and "severity rating" are natural phrases users would say, giving good keyword coverage. Missing natural variations like "vulnerability", "CVSS", "advisory/RHSA", and "patch" keep it below the comprehensive synonym coverage of a 5, but it is clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

"Red Hat's severity rating system" carves out a mostly distinct niche with minor overlap risk against a generic CVE/vulnerability explainer. It is not a 5 because a plain "explain this CVE" request could plausibly route to a non-Red-Hat skill, but it is far above the generic overlap of anchors 2-3.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-basic/skills/red-hat-cve-explainer/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.