What problem does it solve? When a vendor ships a security patch but releases no public PoC or technical details, this Skill lets you work backward from the patched and unpatched binaries to identify what bug was fixed, infer its vulnerability class, and build a proof-of-concept that triggers it on unpatched systems. ## Core Features & Use Cases - Binary Diff Workflow: Step-by-step process for obtaining before/after binaries (MSU/CAB on Windows, deb/rpm on Linux), aligning symbols, and diffing with BinDiff, Diaphora, or ghidriff. - Root Cause Inference Patterns: A lookup table mapping newly added patch code (bounds checks, locks, refcounting, ProbeForRead, zeroing) to bug classes like OOB write, race condition, UAF, integer overflow, and info leak. - PoC Templates and Verification: Concrete trigger strategies per bug class (boundary values, multi-threaded racing, spray-free-reuse) plus the rule that unpatched must crash while patched stays clean. - Use Case: After Patch Tuesday, download the KB for a Windows kernel CVE, diff ntoskrnl.exe across versions, spot a newly added spinlock and refcount check, then write a multi-threaded PoC that wins the race and triggers a double free on the unpatched build. ## Quick Start Ask the agent to diff the patched and unpatched versions of a target binary with ghidriff and infer the vulnerability class from the changed functions.