Security Assessment
amd/gaia
Assess a reported security vulnerability in GAIA and fill a PSIRT / JIRA triage: decide if it is valid & exploitable, whether it needs a CVE + bulletin, and produce the CVSS 4.0 score, CWE, and CVE…
Gather comprehensive vulnerability information from multiple authoritative sources with fallback strategies
$ npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers cve-intelligence-gathering --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/compliance/skills/cve-intelligence-gathering .claude/skills/cve-intelligence-gathering && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cve-intelligence-gathering" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gathering into .claude/skills/cve-intelligence-gathering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-intelligence-gathering", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gatheringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers cve-intelligence-gathering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/compliance/skills/cve-intelligence-gathering .agents/skills/cve-intelligence-gathering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cve-intelligence-gathering" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gathering into .agents/skills/cve-intelligence-gathering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-intelligence-gathering", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers cve-intelligence-gathering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/compliance/skills/cve-intelligence-gathering .cursor/skills/cve-intelligence-gathering && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cve-intelligence-gathering" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gathering into .cursor/skills/cve-intelligence-gathering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-intelligence-gathering", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/compliance/skills/cve-intelligence-gathering--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers cve-intelligence-gathering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/compliance/skills/cve-intelligence-gathering .gemini/skills/cve-intelligence-gathering && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cve-intelligence-gathering" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gathering into .gemini/skills/cve-intelligence-gathering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-intelligence-gathering", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-eng/ai-helpers cve-intelligence-gatheringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/compliance/skills/cve-intelligence-gathering .github/skills/cve-intelligence-gathering && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cve-intelligence-gathering" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gathering into .github/skills/cve-intelligence-gathering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-intelligence-gathering", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers cve-intelligence-gathering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/compliance/skills/cve-intelligence-gathering .opencode/skills/cve-intelligence-gathering && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cve-intelligence-gathering" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/compliance/skills/cve-intelligence-gathering into .opencode/skills/cve-intelligence-gathering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cve-intelligence-gathering", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cve-intelligence-gatheringGather comprehensive vulnerability information from multiple authoritative sources with fallback strategies
Cve Intelligence Gathering is an agent skill from openshift-eng/ai-helpers. Gather comprehensive vulnerability information from multiple authoritative sources with fallback strategies
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Vulnerability scanning. It works with Jira. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
redhat.atlassian.netnvd.nist.govgithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cve Intelligence Gathering loads about 4.1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 1,195 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 1,195 words, ~4,053 tokens.
.claude/skills/cve-intelligence-gathering/SKILL.md (or your agent's skills folder).Systematically collects CVE vulnerability details from multiple authoritative sources, handles search failures, and compiles a comprehensive vulnerability profile for analysis.
Use this skill when:
web_search tool access# Regex pattern for CVE ID
CVE_PATTERN="^CVE-[0-9]{4}-[0-9]{4,}$"
# Validate format
if [[ "$CVE_ID" =~ $CVE_PATTERN ]]; then
echo "Valid CVE format"
else
echo "ERROR: Invalid CVE format. Expected: CVE-YYYY-NNNNN"
exit 1
fiExtract components:
YYYY from CVE-YYYY-NNNNNNNNNN from CVE-YYYY-NNNNNDecision Point:
If a jira_context object was passed in from the jira-cve-extraction skill (i.e. the parent command was invoked with --jira= or --jql=), pre-populate the vulnerability profile before any web searches. This reduces redundant lookups and surfaces internal context that is not available in public databases.
Fields to extract and pre-populate:
| Jira field | Profile field | Notes |
|---|---|---|
cvss_score + cvss_vector | severity.cvss_score, severity.cvss_vector | Prefer Jira value; verify against NVD in Step 2 |
cwe_id | cwe_id | Cross-check with NVD; flag if they differ |
summary (parsed description) | description (supplement) | Internal phrasing may be more specific |
affects_versions | Analysis scope (which project/release versions are affected) | |
target_versions | Fix target / release window | |
release_note_text | remediation.recommended_action (supplement) | May already describe the fix or upgrade path |
components, labels | Context only | |
| Description body (workaround scan) | remediation.workarounds | Already extracted by jira-cve-extraction |
| Internal notes from description | internal_context field in profile | Capture any previous analysis, conclusions, or decisions noted in the ticket body |
Mark each pre-populated field as source: jira in the profile.
Conflict resolution: If Jira and a public source (NVD, GHSA) disagree on CVSS score or CWE:
Decision Point:
jira_context is null or absent (direct <CVE-ID> mode) → Skip this step entirely, proceed to Step 2 as normaljira_context is present → Pre-populate, then continue to Step 2 to fill remaining gaps and verifyNational Vulnerability Database (NVD)
Search query: "CVE-{ID} site:nvd.nist.gov"
Example: "CVE-YYYY-NNNNN site:nvd.nist.gov"Extract from results:
MITRE CVE Database
Search query: "CVE-{ID} site:cve.mitre.org"
Example: "CVE-YYYY-NNNNN site:cve.mitre.org"Extract from results:
Error Handling:
Go Vulnerability Database
Search queries:
1. "CVE-{ID} golang vulnerability"
2. "CVE-{ID} site:github.com/golang/vulndb"
3. "CVE-{ID} site:go.dev/security"Extract from results:
<package-path>)< <version>)<version>)GitHub Security Advisories (GHSA)
Search queries:
1. "CVE-{ID} golang GHSA"
2. "CVE-{ID} site:github.com/advisories"Look for:
GHSA-xxxx-xxxx-xxxx)Decision Point:
Security Advisories
Search queries:
1. "CVE-{ID} security advisory"
2. "CVE-{ID} golang fix"
3. "CVE-{ID} patch"Look for:
Community Discussions
Search queries:
1. "CVE-{ID} golang github issue"
2. "CVE-{ID} golang discussion"Check for:
Proof of Concept / Exploits (for context only)
Search query: "CVE-{ID} exploit poc"Note: Only use for understanding attack vectors, not for testing
If CVE is Very New (e.g., published recently)
Search alternative queries:
1. "CVE-{ID} disclosure"
2. "CVE-{ID} advisory {YEAR}"
3. "{PACKAGE_NAME} vulnerability {YEAR}"If Web Searches Return No Results
Try alternative strategies:
Search by package name (if known from context):
Search: "{package-name} vulnerability {year}"
Example: "<package-name> vulnerability <year>"Search for GHSA aliases:
Search: "GHSA-{pattern} golang"Check package repository directly:
Search: "site:github.com/{org}/{repo} security"Decision Point:
If automated searches fail: IF AUTO_APPROVE=yes → there is no one to prompt; skip straight to "User Response Handling: no" below (return an error to the parent command). This step is never gated to proceed automatically — fabricating CVE details is not a safe default, regardless of how much unattended automation the caller wants. IF AUTO_APPROVE=no (or unset — the default) → prompt user:
❌ Unable to fetch details for {CVE-ID} from online sources.
Attempted searches:
- NVD: No results
- MITRE: No results
- Go vulnerability database: No results
- GitHub Security Advisories: No results
Please provide any information you have about this CVE:
1. CVE Description:
[What vulnerability does this CVE describe?]
2. Affected Go Packages/Modules:
[e.g., <package-path>, github.com/<org>/<repo>]
3. Vulnerable Version Range:
[e.g., all versions before <version>, or versions <version-range>]
4. Fixed Version (if known):
[e.g., <version> or later]
5. Severity (if known):
[CRITICAL/HIGH/MEDIUM/LOW or CVSS score]
6. References (if any):
[Links to security advisories, GitHub issues, etc.]
You can provide partial information. Analysis will proceed with whatever details are available.
Would you like to provide CVE details? (yes/no)User Response Handling:
Merge all gathered information — Jira context (Step 1.5, if present) and public sources (Steps 2–6) — into a single profile. Every field records which source(s) populated it.
{
"cve_id": "CVE-YYYY-NNNNN",
"aliases": ["GHSA-xxxx-xxxx-xxxx"],
"severity": {
"rating": "<CRITICAL|HIGH|MEDIUM|LOW>",
"cvss_score": "<score>",
"cvss_vector": "<CVSS vector string>",
"cvss_source": "<jira|nvd|ghsa — which source this came from>"
},
"affected_packages": [
{
"name": "<package-name>",
"vulnerable_versions": "<version-range>",
"fixed_version": "<fixed-version>",
"vulnerable_functions": ["<function1>", "<function2>"]
}
],
"vulnerability_type": "<vulnerability-type>",
"cwe_id": "CWE-<number>",
"attack_vector": "<attack-vector>",
"description": "<vulnerability description>",
"impact": {
"confidentiality": "<NONE|LOW|HIGH>",
"integrity": "<NONE|LOW|HIGH>",
"availability": "<NONE|LOW|HIGH>"
},
"remediation": {
"fix_available": true,
"recommended_action": "<remediation guidance>",
"workarounds": ["<workaround from Jira description or public advisory>"],
"fix_target_versions": ["<target versions from Jira target_versions, if any>"],
"release_note": "<from Jira release_note_text if present>"
},
"internal_context": {
"jira_ticket": "<PROJ-NNNNN or null>",
"affects_versions": ["<affected versions from Jira>"],
"previous_analysis_notes": "<any conclusions or analysis captured in Jira description>",
"priority": "<Jira priority>",
"status": "<Jira status>"
},
"information_sources": [
{
"type": "Jira",
"verified": true,
"url": "https://redhat.atlassian.net/browse/<PROJ-NNNNN>"
},
{
"type": "NVD",
"verified": true,
"url": "https://nvd.nist.gov/vuln/detail/CVE-YYYY-NNNNN"
},
{
"type": "GitHub Security Advisory",
"verified": true,
"url": "https://github.com/advisories/GHSA-xxxx-xxxx-xxxx"
}
],
"information_completeness": "COMPLETE",
"data_quality": "HIGH",
"conflicts": [],
"gaps": []
}internal_context and the Jira entry in information_sources are only populated when a jira_context was passed in (Step 1.5); omit them entirely in direct <CVE-ID> mode.
Mark Information Sources:
Record conflicts when Jira and public sources disagree:
"conflicts": [
{
"field": "cvss_score",
"jira_value": "7.5",
"public_value": "6.5",
"resolution": "Used higher value (7.5) for conservative risk assessment"
}
]Assess Information Completeness:
Identify Gaps:
"gaps": [
"CVSS score not available",
"Fixed version not confirmed",
"Vulnerable functions not identified"
]Assess if CVE is Go-related:
Strong Indicators (HIGH confidence):
Weak Indicators (MEDIUM confidence):
Not Go-related (Exit early):
Decision Point:
Return structured data to parent command:
{
"skill": "cve-intelligence-gathering",
"status": "success",
"cve_profile": {
"cve_id": "CVE-YYYY-NNNNN",
"severity": "<CRITICAL|HIGH|MEDIUM|LOW>",
"cvss_score": "<score>",
"affected_packages": [...],
"fixed_versions": [...],
"description": "...",
"references": [...]
},
"information_quality": {
"completeness": "<COMPLETE|MOSTLY_COMPLETE|PARTIAL|MINIMAL>",
"sources": ["<source1>", "<source2>", ...],
"user_provided": "<true|false>",
"gaps": []
},
"go_relevance": {
"is_go_related": "<true|false>",
"confidence": "<HIGH|MEDIUM|LOW>",
"reasoning": "<explanation>"
}
}Error: Invalid CVE identifier format
Expected: CVE-YYYY-NNNNN
Received: {user-input}Action: Return error, do not proceed
Warning: CVE-{ID} not found in any database
Possible reasons:
- CVE is very new (not yet published)
- CVE ID is incorrect
- CVE was disputed/rejected
- Private disclosure not yet publicAction: Request user input or exit
Info: CVE-{ID} does not appear to affect Go
Affected platforms: {list}Action: Return NOT_APPLICABLE verdict early
Step 1: Validate
✓ CVE-YYYY-NNNNN - Valid format
Step 2: Primary Sources
✓ NVD: Found - CVSS <score>, Severity: <severity>
✓ MITRE: Found - CWE-<number>, References available
Step 3: Go-Specific Sources
✓ Go vulndb: Found - <package-name>
✓ GHSA: Found - GHSA-xxxx-xxxx-xxxx
- Affected: <package-name> <version-range>
- Fixed: <fixed-version>
- Vulnerable functions: <function1>, <function2>
Step 4: Remediation Intelligence
✓ GitHub Advisory: Update to <fixed-version>
✓ Release notes: <release-notes-url>
✓ Fix commit: <commit-url>
Step 5: Not needed - sufficient data
Step 6: Not needed - sufficient data
Step 7: Compile Profile
✓ All fields populated
✓ Information completeness: COMPLETE
✓ Data quality: HIGH
✓ No gaps identified
Step 8: Go Relevance
✓ Is Go-related: YES
✓ Confidence: HIGH
✓ Package: <package-name>
Result: Complete vulnerability profile ready for Phase 2 analysisThis skill is called from Phase 1 of the analyze-cve skill.
Input from parent:
<CVE-ID> argument, or extracted by jira-cve-extraction when --jira=/--jql= was used)jira_context object from the jira-cve-extraction skill (optional — only present when --jira= or --jql= was provided)AUTO_APPROVE (yes/no, default no) — governs the Step 6 fallback-prompt gatingOutput to parent:
cve_profile — merged vulnerability profile (Jira internal context + public sources when Jira mode was used; public sources only otherwise)information_quality — completeness assessment (noting which fields came from which source)conflict_log — where Jira and public sources disagreed (empty when no Jira context)go_relevance — Go applicability determinationDecision Flow:
IF status = "error" → Exit command
IF go_relevance.is_go_related = false → Generate "Not Applicable" report, exit
IF information_quality.completeness = "MINIMAL" AND user_declined → Exit command
OTHERWISE → Proceed to Phase 2 with profile© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/compliance/skills/cve-intelligence-gathering of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Cve Intelligence Gathering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cve Intelligence Gathering this skillopenshift-eng/ai-helpers | 120 | — | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Security Assessmentamd/gaia | 1.6k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Building Vulnerability Dashboard With Defectdojomukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Shiro Attack CLISummerSec/ShiroAttack2 | 2.6k | — | ~945 | Automated safety check: Pass | MIT | |
| Cve Remediationrundeck/rundeck | 6.3k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
amd/gaia
Assess a reported security vulnerability in GAIA and fill a PSIRT / JIRA triage: decide if it is valid & exploitable, whether it needs a CVE + bulletin, and produce the CVSS 4.0 score, CWE, and CVE…
mukul975/Anthropic-Cybersecurity-Skills
Deploy DefectDojo as a centralized vulnerability management dashboard that ingests findings from 200+ security scanners, deduplicates results, tracks remediation metrics, and integrates with CI/CD…
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
rundeck/rundeck
Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.
mono/SkiaSharp
Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
openshift-eng/ai-helpers
Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
openshift-eng/ai-helpers
Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file
Works with
Categories
Gather comprehensive vulnerability information from multiple authoritative sources with fallback strategies. Cve Intelligence Gathering is an agent skill from openshift-eng/ai-helpers.
Cve Intelligence Gathering fits situations like: tasks that involve Vulnerability scanning.
Run `npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a claude-code`. Or copy the skill folder (plugins/compliance/skills/cve-intelligence-gathering in openshift-eng/ai-helpers) into .claude/skills/cve-intelligence-gathering in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a codex`. Or copy the skill folder (plugins/compliance/skills/cve-intelligence-gathering in openshift-eng/ai-helpers) into .agents/skills/cve-intelligence-gathering in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill cve-intelligence-gathering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cve-intelligence-gathering, .gemini/skills/cve-intelligence-gathering, .github/skills/cve-intelligence-gathering and .opencode/skills/cve-intelligence-gathering in your project.
SKILL.md names no scripts, command-line tools or credentials: Cve Intelligence Gathering is instructions for the agent only.
SKILL.md names 3 domains. In commands or code: redhat.atlassian.net, nvd.nist.gov and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Cve Intelligence Gathering is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cve Intelligence Gathering: Security Assessment (amd/gaia, 1.6k stars), Building Vulnerability Dashboard With Defectdojo (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars) and Shiro Attack CLI (SummerSec/ShiroAttack2, 2.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.
Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.