About redteam
redteam is a structured skill for adversarially assessing a plan, system, or strategy. It organizes attack surfaces, failure modes, assumptions, and mitigations to help identify risks and hardening steps.
Key features
- 01Attack-surface assessment
- 02Technical and human failure analysis
- 03Adversary scenario development
- 04Assumption challenge
- 05Mitigation recommendations
Use cases
- 01Reviewing a system for vulnerabilities
- 02Stress-testing a project plan
- 03Identifying operational failure risks
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/redteamin Claude Code to confirm it loaded.
Details
From the project READMERed Team Analysis
Conduct an adversarial analysis to find weaknesses, vulnerabilities, and failure modes in a plan, system, or strategy.
Instructions
Think like an attacker. Your job is to break this, find the gaps, and expose what could go wrong. Be thorough and creative in your attacks.
Output Format
Target: [What we're attacking] Objective: [What would "breaking it" look like?]
Target Understanding
Summary of the Plan/System [Brief description of what we're analyzing]
Key Assumptions
- [Assumption 1]
- [Assumption 2]
Attack Surface Analysis
Entry Points / Vulnerabilities
| Vector | Description | Severity |
|---|---|---|
| [attack vector] | [how it could be exploited] | Critical/High/Med/Low |
Failure Mode Analysis
Technical/Operational Failures
| Failure Mode | Trigger | Impact |
|---|---|---|
| [what could fail] | [what causes it] | [effect] |
Human Failures
| Failure Mode | Trigger | Impact |
|---|---|---|
| [human error] | [situation] | [consequence] |
Adversary Scenarios
If I wanted this to fail, I would...
Scenario 1: [Attack Name]
- Attack method: [how they'd do it]
- Likelihood of success: [High/Med/Low]
- Impact if successful: [consequences]
Scenario 2: [Attack Name]
- Attack method: [how]
- Likelihood of success: [High/Med/Low]
- Impact if successful: [consequences]
Assumption Attacks
| Assumption | Attack | What If Wrong? |
|---|---|---|
| [assumption] | [challenge to it] | [consequences] |
Blind Spot Analysis
What are we not seeing?
- [Blind spot 1]
- [Blind spot 2]
What are we too optimistic about?
- [Over-optimism 1]
Red Team Findings
Critical Vulnerabilities (Must Address)
| Vulnerability | Risk | Mitigation |
|---|---|---|
| [vulnerability] | [risk level] | [how to fix] |
High-Priority Concerns
| Concern | Recommendation |
|---|---|
| [concern] | [recommendation] |
Hardening Recommendations
Immediate actions:
- [Action 1]
- [Action 2]
Ongoing monitoring:
- [What to watch]
Bottom Line
[Is this plan/system ready? What must change?]
Guidelines
- Be adversarial, not just critical
- Think creatively—real attackers don't follow rules
- Look for cascading failures
- The goal is to make it stronger, not just find flaws
$ARGUMENTS