Dependency Scan
jwynia/agent-skills
Detect CVEs and security issues in project dependencies. An agent skill from jwynia/agent-skills.
容器安全CVE漏洞修复验证引擎。从容器漏扫报告(Excel)自动提取漏洞，生成修复计划， SSH到测试环境验证OS包(apt/yum/apk)、Python(pip)、Node.js(npm)、Java(JAR)四种包类型的 修复方案，产出修复验证报告。不涉及主机层漏洞修复、不处理容器编排层安全配置。
Install Container Cve Fix Validator
$ npx skills add infometa/workbuddyskills --skill container-cve-fix-validator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills container-cve-fix-validator --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/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator .claude/skills/container-cve-fix-validator && 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 "container-cve-fix-validator" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator into .claude/skills/container-cve-fix-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-cve-fix-validator", 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/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validatorType 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 infometa/workbuddyskills --skill container-cve-fix-validator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills container-cve-fix-validator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator .agents/skills/container-cve-fix-validator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "container-cve-fix-validator" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator into .agents/skills/container-cve-fix-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-cve-fix-validator", 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 infometa/workbuddyskills --skill container-cve-fix-validator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills container-cve-fix-validator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator .cursor/skills/container-cve-fix-validator && 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 "container-cve-fix-validator" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator into .cursor/skills/container-cve-fix-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-cve-fix-validator", 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/infometa/workbuddyskills.git --path experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator--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 infometa/workbuddyskills --skill container-cve-fix-validator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills container-cve-fix-validator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator .gemini/skills/container-cve-fix-validator && 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 "container-cve-fix-validator" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator into .gemini/skills/container-cve-fix-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-cve-fix-validator", 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 infometa/workbuddyskills container-cve-fix-validatorInstalls 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 infometa/workbuddyskills --skill container-cve-fix-validator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator .github/skills/container-cve-fix-validator && 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 "container-cve-fix-validator" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator into .github/skills/container-cve-fix-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-cve-fix-validator", 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 infometa/workbuddyskills --skill container-cve-fix-validator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills container-cve-fix-validator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator .opencode/skills/container-cve-fix-validator && 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 "container-cve-fix-validator" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator into .opencode/skills/container-cve-fix-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-cve-fix-validator", 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.
Facts
- Skill name
container-cve-fix-validator- GitHub stars
- 346
- Token cost
- ~779 tokens
- SKILL.md length
- 152 words
- Files
- 30 (incl. scripts, references)
- Skills in repo
- 218
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
容器安全CVE漏洞修复验证引擎。从容器漏扫报告(Excel)自动提取漏洞，生成修复计划， SSH到测试环境验证OS包(apt/yum/apk)、Python(pip)、Node.js(npm)、Java(JAR)四种包类型的 修复方案，产出修复验证报告。不涉及主机层漏洞修复、不处理容器编排层安全配置。
- Works in 5 steps: 分析 fix_guidance.fix_suggestion 理解问题 → 从 available_versions 选最佳版本 → 执行 apply_fix_cmd 修正 → …
- Tasks that involve Vulnerability scanning
- SKILL.md covers 角色, 四步流水线, 安全版本验证 and 配置, plus 2 more sections
- Runs Python scripts from its folder; calls python3; needs SSH_PASSWORD and NVD_API_KEY
What it does
Container Cve Fix Validator is an agent skill from infometa/workbuddyskills. 容器安全CVE漏洞修复验证引擎。从容器漏扫报告(Excel)自动提取漏洞，生成修复计划， SSH到测试环境验证OS包(apt/yum/apk)、Python(pip)、Node.js(npm)、Java(JAR)四种包类型的 修复方案，产出修复验证报告。不涉及主机层漏洞修复、不处理容器编排层安全配置。 触发关键词：容器漏扫、CVE验证、漏洞修复验证、container CVE、fix validation。
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 32 other files, including scripts and reference files (for example `README.md`, `references/config-guide.md` and `references/output-schema.json`).
It sits in Security, covering Vulnerability scanning and Excel spreadsheets. It works with Microsoft Excel, npm, Java and Python. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Vulnerability scanning
- Tasks that involve Excel spreadsheets
Example prompts
- “/container-cve-fix-validator”
Requirements
- Python 3
- Node.js
- A credential in NVD_API_KEY
- Pre-approved tools (allowed-tools): Read, Write, Bash, Glob, Grep
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 分析 fix_guidance.fix_suggestion 理解问题
- 从 available_versions 选最佳版本
- 执行 apply_fix_cmd 修正
- 用 --next --task-id <同ID> 重跑
- 修正成功后继续下一条
What it can do on your machine
Read from SKILL.md and the folder at commit 692b3eb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteBashGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 9 files in scripts/ (Python, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SSH_PASSWORDNVD_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Container Cve Fix Validator loads about 779 tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 152 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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:100
所有配置通过环境变量注入。复制 `.env.example` 为 `.env` 或直接 `export`。 - NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Bash, Glob, Grep
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); the scripts in this folder are not scanned.
SKILL.md
The full file from infometa/workbuddyskills at commit 692b3eb, republished under its Apache-2.0 licence (© infometa). 152 words, ~779 tokens.
Download SKILL.mdSave it as
.claude/skills/container-cve-fix-validator/SKILL.md (or your agent's skills folder). This skill also uses 29 other files; get the full folder from GitHub.- name
- container-cve-fix-validator
- description
- 容器安全CVE漏洞修复验证引擎。从容器漏扫报告(Excel)自动提取漏洞，生成修复计划， SSH到测试环境验证OS包(apt/yum/apk)、Python(pip)、Node.js(npm)、Java(JAR)四种包类型的 修复方案，产出修复验证报告。不涉及主机层漏洞修复、不处理容器编排层安全配置。 触发关键词：容器漏扫、CVE验证、漏洞修复验证、container CVE、fix validation。
- allowed-tools
- Read, Write, Bash, Glob, Grep
- version
- 1.0.0
- triggers
- 容器漏扫, 容器CVE, container CVE, fix validation, 容器修复
- disable
- false
容器安全CVE漏洞修复验证
角色
执行容器安全修复验证流水线。接收容器漏扫 Excel 报告，逐条在测试环境验证每个 CVE 的可修复性，出具验证结论报告。禁止跳过、合并、或自行判断"这个不用验"。
四步流水线
步骤1: parse_container_report.py → vulns.json
步骤2: run_pipeline.py --create-plan → execution_plan.json (+ OVAL 自动增强)
步骤3: run_pipeline.py --next --task-id N → 逐条循环（看返回决策）
步骤4: run_pipeline.py --summary → 汇总报告 + 自动打包辅助命令（随时可用）：--status 查看进度、--list 列出所有任务。
步骤1：解析报告
python3 scripts/parse_container_report.py "<Excel完整路径>" -o $HOME/tmp/cve_fix_test/vulns.json读取 vulns.json，向用户汇报漏洞摘要表格（CVE、组件、版本、镜像、严重程度）。
步骤2：创建计划 + OVAL 自动增强
python3 scripts/run_pipeline.py --create-plan $HOME/tmp/cve_fix_test/vulns.json关注返回字段：total_tasks、pkg_type_stats、next_task_id。
本步骤只调这一条命令。不要先跑
--help，不要先查 CVE。
步骤3：逐条执行（一次一条）
python3 scripts/run_pipeline.py --next --task-id <N>循环退出判断：看 next_action
next_action | 含义 | 操作 |
|---|---|---|
call_next_tool_once | 继续 | 用 next_task_id 再调 --next |
run_summary | 全部完成 | 执行步骤4 --summary |
SKIPPED 状态：next_task_id 直接指向下一个 pending，按指引继续即可。
失败处理：当 status=FAILED 时返回含 fix_guidance：
- 分析
fix_guidance.fix_suggestion理解问题 - 从
available_versions选最佳版本 - 执行
apply_fix_cmd修正 - 用
--next --task-id <同ID>重跑 - 修正成功后继续下一条
严禁 shell 循环批量。失败必须修正，不得跳过。 12 种失败分类明细见
references/pipeline-detail.md。
步骤4：汇总报告 + 自动打包
python3 scripts/run_pipeline.py --summary拦截机制：仍有 pending/in_progress 任务时返回 blocked=true，必须继续 --next。
安全版本验证
| 结果 | 含义 |
|---|---|
CONFIRMED_SAFE | installed_version >= fix_versions |
LIKELY_SAFE | 版本有提升但无权威基线验证 |
STILL_VULNERABLE | installed_version < fix_versions → 需修正 |
数据源优先级：OVAL → CIRCL → NVD（详见 references/ovalfeeds-guide.md）
配置
所有配置通过环境变量注入。复制 .env.example 为 .env 或直接 export。
必填：SSH_HOST、SSH_PASSWORD（SSH 验证阶段4）
可选：DOCKER_REGISTRY、YUM_SOURCES_*、APT_SOURCES_*、NVD_API_KEY
完整参数说明见 .env.example 和 references/config-guide.md。
操作守则
- 仅调用白名单脚本：
parse_container_report.py、run_pipeline.py、apply_fix.py、package_and_upload.py、oval_query.py。内部脚本由上述脚本子进程调起，AI 不直接调用。 --next一次一条：严禁 shell for 循环批量。- 失败必须修正：
fix_guidance提供了修正命令，必须尝试执行。 - pending 未清零前不得汇报"已完成"：
--summary返回blocked=true时必须继续--next。 - 禁止编造数据：脚本失败时如实报告。
- 输出路径始终使用
$HOME/tmp/cve_fix_test/：禁止向项目目录写文件。
参考文档
| 文档 | 说明 |
|---|---|
references/pipeline-detail.md | 完整 JSON 结构、12类失败明细、输出目录结构 |
references/config-guide.md | 配置指南（环境变量完整说明） |
references/ovalfeeds-guide.md | OVAL feeds 管理操作手册 |
references/output-schema.json | 输出 JSON Schema |
references/report-template.md | 报告模板 |
© infometa, 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
Files
SKILL.md and 29 other files (scripts, references) in experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator of infometa/workbuddyskills.
- SKILL.md
- LICENSE
- README.md
- references/config-guide.md
- references/output-schema.json
- references/ovalfeeds-guide.md
- references/pipeline-detail.md
- references/report-template.md
- requirements.txt
- scripts/analyze_cve.py
- scripts/apply_fix.py
- scripts/assess_target_version.py
- scripts/data_dir.py
- scripts/feeds/__init__.py
- scripts/feeds/feed_manager.py
- scripts/feeds/manifest.json
- scripts/feeds/oval_db.py
- scripts/feeds/oval_parser.py
- … and 12 more
Open the folder on GitHubat commit 692b3eb
Compare with similar skills
Container Cve Fix Validator 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 |
|---|---|---|---|---|---|---|
| Container Cve Fix Validator this skillinfometa/workbuddyskills | 346 | — | ~779 | Automated safety check: Notes | Apache-2.0 | |
| Dependency Scanjwynia/agent-skills | 169 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Streaming Export Safetydoccker/cc-use-exp | 1.1k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Release Coherencemacalbert/envilder | 138 | — | ~1.3k | Automated safety check: Pass | MIT | |
| CodeQL Security Scantrailofbits/skills | 7.4k | — | ~4.6k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Security Verification Gatefengshao1227/ccg-workflow | 5.9k | — | ~621 | Automated safety check: Notes | MIT |
Similar skills
Streaming Export Safety
doccker/cc-use-exp
当代码涉及 Excel/CSV/JSON/PDF 大文件导出、批量序列化、内存里构建大对象时触发。防止 OOM、临时文件残留、同步导出阻塞 HTTP 线程等内存安全陷阱。
Release Coherence
macalbert/envilder
Unified release coherence workflow for any component (CLI, GHA, or SDK).
- Official
CodeQL Security Scan
trailofbits/skills
Scans a codebase for vulnerabilities with CodeQL's data flow and taint tracking in run-all or important-only modes, including data extensions for project-specific sources and sinks.
Security Verification Gate
fengshao1227/ccg-workflow
Scans code with a bundled Node script for injection, secrets, XSS and other risky patterns, ranks findings by severity and checks that security decisions are documented.
Security Audit
TheDecipherist/claude-code-mastery
Checks a codebase for hardcoded secrets, vulnerable dependencies, weak input handling, weak authentication and unsafe transport settings before deployment or merge.
More from infometa/workbuddyskills
All 218 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Related
Works with
Categories
Questions about Container Cve Fix Validator
What does Container Cve Fix Validator do?
容器安全CVE漏洞修复验证引擎。从容器漏扫报告(Excel)自动提取漏洞，生成修复计划， SSH到测试环境验证OS包(apt/yum/apk)、Python(pip)、Node.js(npm)、Java(JAR)四种包类型的 修复方案，产出修复验证报告。不涉及主机层漏洞修复、不处理容器编排层安全配置。. Container Cve Fix Validator is an agent skill from infometa/workbuddyskills.
When should I use Container Cve Fix Validator?
Container Cve Fix Validator fits situations like: tasks that involve Vulnerability scanning; tasks that involve Excel spreadsheets.
How do I install Container Cve Fix Validator in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill container-cve-fix-validator -a claude-code`. Or copy the skill folder (experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator in infometa/workbuddyskills) into .claude/skills/container-cve-fix-validator in your project. Claude Code loads it when a task matches its description.
How do I install Container Cve Fix Validator in Codex?
Run `npx skills add infometa/workbuddyskills --skill container-cve-fix-validator -a codex`. Or copy the skill folder (experts/soe/skills/soe/references/vulnerability-analysis/container-cve-fix-validator in infometa/workbuddyskills) into .agents/skills/container-cve-fix-validator in your project. Codex loads it when a task matches its description.
Can I use Container Cve Fix Validator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add infometa/workbuddyskills --skill container-cve-fix-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/container-cve-fix-validator, .gemini/skills/container-cve-fix-validator, .github/skills/container-cve-fix-validator and .opencode/skills/container-cve-fix-validator in your project.
What does Container Cve Fix Validator need to run?
Going by SKILL.md and its folder, Container Cve Fix Validator needs Python for the scripts in its folder, the command-line tools its instructions call (python3) and credentials named SSH_PASSWORD and NVD_API_KEY. Our summary lists: Python 3; Node.js; A credential in NVD_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Bash, Glob, Grep.
Does Container Cve Fix Validator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Container Cve Fix Validator safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Container Cve Fix Validator use?
Container Cve Fix Validator is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Container Cve Fix Validator use?
About 779 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.
What are the alternatives to Container Cve Fix Validator?
Skills that share tags, products or a category with Container Cve Fix Validator: Dependency Scan (jwynia/agent-skills, 169 stars), Streaming Export Safety (doccker/cc-use-exp, 1.1k stars), Release Coherence (macalbert/envilder, 138 stars) and CodeQL Security Scan (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Container Cve Fix Validator?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 346 GitHub stars. The repository holds 218 skills in this directory. The repository was last updated on October 8, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.