redteam

Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "redteam" with this command: npx skills add neurofoo/agent-skills/neurofoo-agent-skills-redteam

Red 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

VectorDescriptionSeverity
[attack vector][how it could be exploited]Critical/High/Med/Low

Failure Mode Analysis

Technical/Operational Failures

Failure ModeTriggerImpact
[what could fail][what causes it][effect]

Human Failures

Failure ModeTriggerImpact
[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

AssumptionAttackWhat 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)

VulnerabilityRiskMitigation
[vulnerability][risk level][how to fix]

High-Priority Concerns

ConcernRecommendation
[concern][recommendation]

Hardening Recommendations

Immediate actions:

  1. [Action 1]
  2. [Action 2]

Ongoing monitoring:

  1. [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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

feynman

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

socratic

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

scamper

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

jtbd

No summary provided by upstream source.

Repository SourceNeeds Review