What problem does it solve? Security researchers often prove a low-impact primitive (file write, SSRF, file read) but struggle to determine whether it escalates to remote code execution or should be banked as a gadget. This Skill provides a structured methodology for chaining primitives into RCE and deciding when escalation is worth pursuing. ## Core Features & Use Cases - Chain Playbooks: Documented escalation paths including headless Chrome DevTools to Kubernetes secrets, Perforce file write to DLL hijack, SSRF to cloud metadata credentials, and vulnerable component CVE exploitation. - Gadget Inventory Discipline: Guidance on recording proven-but-low-impact primitives as reusable chain components rather than discarding them. - AI-Assisted Triage Guardrails: Rules for using models to hypothesize source-to-sink reachability and CVE candidates, with mandatory runtime verification and independent CVE confirmation against OSV.dev/NVD. - Use Case: During an authorized bug bounty engagement, you confirm an arbitrary file write on a target. Use this Skill to map the write to escalation paths (webshell, cron, DLL hijack), demonstrate the primitive safely, and explain the RCE path in your report without executing destructive payloads. ## Quick Start Ask the assistant to assess whether a proven file write primitive on an authorized target can be chained to remote code execution and what evidence to collect.
