danielmiessler
Adversarial analysis with 32 agents. USE WHEN red team, attack idea, counterarguments, critique, stress test. SkillSearch('redteam') for docs.
bunx add-skill danielmiessler/personal_ai_infrastructure -s RedTeamLoading…
Before executing, check for user customizations at:
~/.claude/skills/CORE/USER/SKILLCUSTOMIZATIONS/RedTeam/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
You MUST send this notification BEFORE doing anything else when this skill is invoked.
Send voice notification:
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow in the RedTeam skill to ACTION"}' \
> /dev/null 2>&1 &
Output text notification:
Running the **WorkflowName** workflow in the **RedTeam** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
Military-grade adversarial analysis using parallel agent deployment. Breaks arguments into atomic components, attacks from 32 expert perspectives (engineers, architects, pentesters, interns), synthesizes findings, and produces devastating counter-arguments with steelman representations.
Route to the appropriate workflow based on the request.
When executing a workflow, output this notification directly:
Running the **WorkflowName** workflow in the **RedTeam** skill to ACTION...
| Trigger | Workflow |
|---|---|
| Red team analysis (stress-test existing content) | Workflows/ParallelAnalysis.md |
| Adversarial validation (produce new content via competition) | Workflows/AdversarialValidation.md |
| Workflow | Purpose | Output |
|---|---|---|
| ParallelAnalysis | Stress-test existing content | Steelman + Counter-argument (8-points each) |
| AdversarialValidation | Produce new content via competition | Synthesized solution from competing proposals |
The Five-Phase Protocol (ParallelAnalysis):
Philosophy.md - Core philosophy, success criteria, agent typesIntegration.md - Skill integration, FirstPrinciples usage, output formatAttack an architecture proposal:
User: "red team this microservices migration plan"
--> Workflows/ParallelAnalysis.md
--> Returns steelman + devastating counter-argument (8 points each)
Devil's advocate on a business decision:
User: "poke holes in my plan to raise prices 20%"
--> Workflows/ParallelAnalysis.md
--> Surfaces the ONE core issue that could collapse the plan
Adversarial validation for content:
User: "battle of bots - which approach is better for this feature?"
--> Workflows/AdversarialValidation.md
--> Synthesizes best solution from competing ideas
Last Updated: 2025-12-20
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.