メニュー
Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | redteam |
| description | Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect. |
| user-invocable | true |
Conduct an adversarial analysis to find weaknesses, vulnerabilities, and failure modes in a plan, system, or strategy.
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.
Target: [What we're attacking] Objective: [What would "breaking it" look like?]
Summary of the Plan/System [Brief description of what we're analyzing]
Key Assumptions
Entry Points / Vulnerabilities
| Vector | Description | Severity |
|---|---|---|
| [attack vector] | [how it could be exploited] | Critical/High/Med/Low |
| Failure Mode | Trigger | Impact |
|---|---|---|
| [what could fail] | [what causes it] | [effect] |
| Failure Mode | Trigger | Impact |
|---|---|---|
| [human error] | [situation] | [consequence] |
If I wanted this to fail, I would...
| Assumption | Attack | What If Wrong? |
|---|---|---|
| [assumption] | [challenge to it] | [consequences] |
What are we not seeing?
What are we too optimistic about?
| Vulnerability | Risk | Mitigation |
|---|---|---|
| [vulnerability] | [risk level] | [how to fix] |
| Concern | Recommendation |
|---|---|
| [concern] | [recommendation] |
Immediate actions:
Ongoing monitoring:
Bottom Line
[Is this plan/system ready? What must change?]
$ARGUMENTS
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
Cynefin sense-making framework categorizing problems as Simple, Complicated, Complex, Chaotic, or Confused to select the right approach. Use when unsure how to tackle a problem.
