redteam-mindset

What problem does it solve?

This Skill prevents common red-team decision mistakes (premature stopping, retraction on first failure, and scope confusion) so authorized operators stay focused on correctness and access-yielding outcomes.

Core Features & Use Cases

• Scope-discipline for red team vs bug bounty/WAPT: Applies different “win conditions” when engagement scope is external red team, adversary emulation, or assume-breach, rather than using bug-bounty or compliance logic.
• Finding-correctness mindset: Emphasizes verification discipline (don’t retract on first reproducibility failure; treat delta changes as evidence; cross-validate signals with multiple techniques).
• Persistence through blockers: Replaces self-throttling habits with structured decision trees for common obstacles (captcha, WAF, rate limits, timing issues) while keeping the goal fixed.
• Engagement operations clarity: Guides real-engagement cadence (full surface sweeps per host, robots/sitemap/JS/OpenAPI checks, sister-app pivots, evidence journaling) and defines legitimate vs illegitimate stop conditions.

Quick Start

Use the redteam-mindset skill at the start of an external red-team engagement and again whenever you want to stop or retract after a blocker, to keep your tests aligned with “gain access, prove impact” instead of “find a bug and write a report.”