common-exploit-verification

Validate security findings and construct exploit proofs with PoC details.

Updated Jun 25, 2026

Search Tags:#security testing #proof of concept #vulnerability management #false positive #exploit verification

Ready to run

npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill common-exploit-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: common-exploit-verification
Source: https://github.com/VSF-QC-TTS/vf-qc-copilot/tree/main/.agents/skills/common/common-exploit-verification
Command: npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill common-exploit-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires [], and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures "No Exploit, No Report" policy with PoC construction standards, false-positive filtering, and evidence collection across different platforms. It's used for validating security findings, constructing exploit proofs, and writing pentest findings.

Core Features & Use Cases

Exploit Verification: Enforces "No Exploit = No Report" policy with specific rules.
PoC Construction: Provides guidelines for creating PoCs, including all necessary details.
False Positive Filtering: Offers a checklist to filter out false positives before reporting.
Security Evidence Collection: Standardizes the process of collecting evidence for each vulnerability class.

Quick Start

Run the skill with the keyword 'exploit verification' and follow the PoC construction guidelines to verify a security finding.

Frequently Asked Questions about common-exploit-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify a vulnerability and construct a proof of concept?▼

To filter false positives before reporting, the skill provides a specific checklist to validate findings and ensure only confirmed vulnerabilities with constructed exploit proofs are documented.

What is the best way to collect security evidence for a pentest report?▼

The best way to collect security evidence for a pentest report is to standardize the process using the skill's evidence collection guidelines, which are tailored for each different vulnerability class across platforms.

Can I use this exploit verification process for vulnerabilities across different platforms?▼

Yes, you can use this exploit verification process for vulnerabilities across different platforms, as the skill standardizes security evidence collection and PoC construction regardless of the specific target environment.

Do I need to provide proof of concept details to validate a security finding?▼

Yes, you need to provide proof of concept details and vulnerability specifics to proceed, because the skill requires this input to validate security findings and construct the exploit proof.

Why should I enforce a No Exploit No Report policy for security testing?▼

You should enforce a No Exploit No Report policy for security testing to ensure all reported findings are valid, which prevents reporting false positives and requires constructing a proof of concept for every vulnerability.