unclecheng-li/vulnclaw/redteam-cve-validation
Claude Code and agent skill by unclecheng-li/vulnclaw
- community
Checking that the SKILL.md file is still in the repository.
CVE validation domain card. Use after CVE lookup has produced applicable or candidate CVEs and red-team mode needs scoped evidence to decide whether to continue, pivot, or report.
Install
npx vskill@latest install unclecheng-li/vulnclaw/redteam-cve-validationSKILL.md
The same SKILL.md was published earlier as unclecheng-li/vulnclaw/redteam-cve-validation.
CVE Validation
Domain
Validate candidate CVEs against the current target evidence without assuming exploitability. The module consumes cve_candidate_list, product/version evidence, service fingerprints, and scope data, then decides whether the CVE path is usable, patched, not applicable, or needs more recon.
Trigger
Feedback Gates
- Scope Gate: target and asset must be in the declared authorization boundary.
- Evidence Gate: candidate CVE must map to observed product, version, endpoint, service, or fingerprint evidence.
- Applicability Gate: version range, configuration, and reachable component must plausibly match.
- Patch Gate: observed version or vendor advisory must not prove the issue fixed.
- Execution Gate: active validation requires a registered scoped adapter; missing adapters block rather than pretending execution happened.
Boundaries
- Do not run destructive or broad exploit attempts.
- Do not validate outside the declared target and scope.
- Do not treat CVE names alone as proof.
- Prefer passive or low-noise confirmation first.
- If evidence is insufficient, return to recon or CVE lookup rather than guessing.
Pivot Hints
- Candidate has no product/version match -> return to recon-intake for better fingerprinting.
- Candidate is patched or not applicable -> route by highest-ranked attack surface from recon.
- Tool or adapter missing -> record missing capability and request/choose an equivalent adapter.
- Too many candidates -> rank by reachable component, confidence, impact, and version fit.
Exit Conditions
- Confirmed applicable candidate -> continue to the specific validation/testing skill.
- All candidates patched/not applicable -> exit to evidence-based router.
- Evidence incomplete -> return to recon-intake or cve-lookup.
- Required tool/scope/adapter missing -> block with the missing capability or scope evidence.
Exit Evidence
- Required: cve_validation_result
- Optional: cve_patch_status, applicability_proof, non_applicability_reason
- min_attempts: 1
Capabilities
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingvulnclaw/skills/specialized/redteam-cve-validation/SKILL.md
Popularity
- Repository stars
- 2,920
- Repository forks
- 394
- 7-day trend score
- 40
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/unclecheng-li/vulnclaw/redteam-cve-validation)