How do I install the Red Team Review skill?

Run npx skillmds@latest add richfrem/red-team-review-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Red Team Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Red Team Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Red Team Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Red Team Review?

richfrem (@richfrem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Red Team Review by richfrem — Agent Skill

Name: Red Team Review
Author: richfrem

Red Team Review

(Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved.

richfrem Updated Sep 17, 2026

File contents

Red Team Review Loop

An iterative review loop where research is bundled via context-bundler and dispatched to one or more adversarial reviewers. The loop continues until the red team approves.

When to Use

Architecture or design decisions that need adversarial scrutiny
Research findings that need epistemic validation
Security analysis that needs independent verification
Any work product where "more eyes" reduce risk

Process Flow

Research & Analyze — Deep-dive into the problem domain. Create analysis docs, capture sources.
Review Packet Generation — Prepare the context for the reviewer:
- Create Prompt: Write or update a red-team-prompt.md explaining exactly what is being reviewed and what the reviewer should focus on.
- Define Manifest: Update a manifest.json or equivalent list dictating which source files and research artifacts to include.
- Bundle Context: Execute the context-bundler plugin, feeding it the manifest and prompt, to compile a single cohesive review packet.
Dispatch to Reviewers — Send the bundle to:
- Human reviewers (paste-to-chat or browser)
- CLI agents with adversarial personas (security auditor, devil's advocate)
- Browser-based agents for interactive review
Receive Feedback — Capture the red team's verdict:
- "More Research Needed" → Loop back to step 1 with targeted questions
Completion & Handoff — Once the Red Team verdicts "Approved":
- Terminate the review loop.
- Pass the final, approved research and feedback documents back to the Orchestrator.
- DO NOT attempt to seal the session or run a retrospective. The Orchestrator handles that.

Dependencies

context-bundler — Required for creating review packets
Personas — Adversarial personas in personas/ directory (e.g., security-audit.md, architect-review.md)

Diagram

See: red_team_review_loop.mmd

---name: red-team-review-2description: (Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved.---# Red Team Review LoopAn iterative review loop where research is bundled via `context-bundler` and dispatched to one or more adversarial reviewers. The loop continues until the red team approves.## When to Use- Architecture or design decisions that need adversarial scrutiny- Research findings that need epistemic validation- Security analysis that needs independent verification- Any work product where "more eyes" reduce risk## Process Flow1. **Research & Analyze** — Deep-dive into the problem domain. Create analysis docs, capture sources.2. **Review Packet Generation** — Prepare the context for the reviewer: - **Create Prompt**: Write or update a `red-team-prompt.md` explaining exactly what is being reviewed and what the reviewer should focus on. - **Define Manifest**: Update a `manifest.json` or equivalent list dictating which source files and research artifacts to include. - **Bundle Context**: Execute the `context-bundler` plugin, feeding it the manifest and prompt, to compile a single cohesive review packet.3. **Dispatch to Reviewers** — Send the bundle to: - Human reviewers (paste-to-chat or browser) - CLI agents with adversarial personas (security auditor, devil's advocate) - Browser-based agents for interactive review4. **Receive Feedback** — Capture the red team's verdict: - **"More Research Needed"** → Loop back to step 1 with targeted questions5. **Completion & Handoff** — Once the Red Team verdicts "Approved": - Terminate the review loop. - Pass the final, approved research and feedback documents back to the Orchestrator. - **DO NOT** attempt to seal the session or run a retrospective. The Orchestrator handles that.## Dependencies- **`context-bundler`** — Required for creating review packets- **Personas** — Adversarial personas in `personas/` directory (e.g., `security-audit.md`, `architect-review.md`)## DiagramSee: [red_team_review_loop.mmd](../../resources/diagrams/red_team_review_loop.mmd)

Frequently asked questions