Adversarial finding verification with empirical testing. Load when acting as skeptic, presenter, or arbiter in the /verify-finding workflow. Provides false positive patterns, Playwright empirical testing guide, debate templates, and CVSS calibration for finding verification.
Complete Go backend development patterns including table-driven tests, mocking, observability (tracing, logging, metrics), and HTTP handler patterns.
Organize and scaffold penetration testing workspaces with mandatory authorization gates. Use whenever the user is starting, tracking, or organizing a security assessment, pentest, vulnerability analysis, bug bounty investigation, red team exercise, API security test, web app security review, infrastructure audit, container security scan, cloud security assessment, source code review, security research, or any activity involving active testing, reconnaissance, or vulnerability discovery against a target system. This skill MUST be consulted before creating any test plans, findings, evidence folders, or audit trails. Use it even if the user only says "let's test this" or "check if this is secure".
Turn penetration test evidence, weak drafts, screenshots, scanner output, and notes into reviewer-ready findings and report prose for pentest deliverables. Use when drafting, rewriting, splitting, merging, or polishing findings, executive summaries, scope, methodology, rules of engagement, or related report sections. Do not use for exploit development, active scanning, or generic editing unrelated to security reporting.