What problem does it solve? Writing a clear, evidence-driven vulnerability report for a confirmed security bug is time-consuming and error-prone; this Skill turns one confirmed finding into a disclosure-ready GitHub advisory with consistent structure and verifiable evidence. ## Core Features & Use Cases - Structured Report Generation: Produces a report with required sections (Summary, Details, Root Cause, Proof of Concept, Impact) following a defined template. - Evidence Linking: Embeds fenced code snippets and GitHub markdown links pinned to commit SHAs so source references remain stable. - Severity-Based Organization: Saves each report as report.md inside a folder named with a severity ID (C1, H1, M1) and title slug, skipping Low severity findings. - Use Case: After confirming a cross-site WebSocket hijacking bug in a repository, use this Skill to produce a self-contained advisory with PoC steps, root cause analysis, and linked source evidence ready to paste into a GitHub security advisory. ## Quick Start Write a disclosure-ready vulnerability report for the confirmed bug I just validated in this repository.