sd-red-team

Reviews artifacts adversarially and produces classified findings with counterargument analysis.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-red-team-platypeeps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-red-team
Source: https://github.com/platypeeps/sd-ai-command-pack/tree/main/contrib/sd-red-team
Command: npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-red-team-platypeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Settled proposals, plans, and conclusions often carry hidden assumptions, unexamined incentives, and untested failure modes that friendly review misses. This Skill applies a disciplined adversarial review that steelmans the artifact first, then challenges it across relevant lanes while keeping speculation, demonstrated defects, and value disagreements clearly separated. ## Core Features & Use Cases - Steelman-first adversarial review: Builds the strongest fair case for the artifact before criticizing it, so findings target real weaknesses rather than strawmen. - Classified finding register: Assigns every finding exactly one class (demonstrated-defect, plausible-risk, speculative-case, or value-disagreement) with evidence IDs, severity rationale, and closure criteria. - Coverage map and counterargument analysis: Discloses which adversarial lanes were tested, tests the strongest counterargument, and states what evidence would reverse each conclusion. - Use Case: Before approving a security-sensitive architecture proposal, run an adversarial review with a threat frame and restricted sensitivity to surface plausible risks, misuse scenarios, and reversal conditions without exposing exploit detail. ## Quick Start Ask the AI to red-team the attached proposal with a skeptical-reader frame at standard depth and standard sensitivity.

Frequently Asked Questions about sd-red-team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial review of a proposal or plan?▼

Provide the artifact, its intended outcome, audience, and a challenge frame such as threat, incentive, or skeptical-reader. The review steelmans the artifact, tests relevant adversarial lanes, and returns a classified finding register with counterargument analysis and closure evidence.

What is the difference between red-team review and fact-checking?▼

Red-team review challenges an artifact's assumptions, incentives, failure modes, and counterarguments as a whole, while fact-checking verifies individual claims against sources. Use claim-by-claim verification tools for factual accuracy and adversarial review for stress-testing reasoning and risk.

How are red-team findings classified by confidence?▼

Each finding receives exactly one class: demonstrated-defect for evidence-backed failures, plausible-risk for credible but unproven mechanisms, speculative-case for hypothetical scenarios, or value-disagreement for conflicts over goals and priorities. Classes are never blended.

Can adversarial review handle sensitive security details?▼

Yes, a sensitivity policy of minimal, restricted, or standard caps the detail shown to the authorized audience. The review describes affected boundaries and defensive validation while omitting secrets, live targets, and weaponized exploit instructions.

When should I not use adversarial review?▼

Avoid it for claim-by-claim verification, rubric-based scoring, prospective plan failure discovery, or after-action causal analysis, which have dedicated workflows. It also does not grant approval, probe systems, or implement mitigations.