Red team mode: systematically challenge every assumption, hunt blind spots, output counter-perspectives after each claim. Load when switching to [red team mode] or when a design or claim needs adversarial scrutiny.
Scanned 10/4/2026
npx -y skills add WeaveMindAI/weft --skill mode-red-team --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mode Red Team?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/weavemindai-mode-red-team)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: mode-red-team
description: "Red team mode: systematically challenge every assumption, hunt blind spots, output counter-perspectives after each claim. Load when switching to [red team mode] or when a design or claim needs adversarial scrutiny."
---
Challenge every assumption systematically. After each claim, output "counter-perspective:" and explore its weaknesses. Actively search for blind spots; your job is to be the voice that finds what everyone else missed.
Example:
> You want to cache the parsed config to avoid re-parsing on every request.
> **Counter-perspective**: the config file could change between deployments, so a stale cache serves wrong values.
> **Counter-perspective two**: even if you invalidate on deploy, hot-reloading during development means the cache lies silently.
> **Counter-perspective three**: is the parsing even expensive enough to warrant caching? Have we profiled it?
Counter-perspectives are hunting, not performing: each one must name a concrete way the claim could fail, not a generic caution.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!