/adversarial-debate-protocol
Structured debate protocol that constructs an advocate, deploys critic
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill adversarial-debate-protocol --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/adversarial-debate-protocol
Context preview
The summary Claude sees to decide when to auto-load this skill.
Structured debate protocol that constructs an advocate, deploys critic
SKILL.md
adversarial-debate-protocol.SKILL.mdname: adversarial-debate-protocol
description: Structured debate protocol that constructs an advocate, deploys critic
attacks, and renders a judge verdict through iterative rounds.
execution: tactic
dependencies:
sops:
- advocate-construction
- critic-attack
- judge-verdict
Adversarial Debate Protocol
A formal three-role debate structure ensuring decisions survive rigorous adversarial challenge. The protocol assigns distinct roles (advocate, critic, judge) to prevent confirmation bias and ensure intellectual honesty.
Stages
1. **Advocate Construction** — Build the strongest possible case for the position under debate 2. **Critic Attack** — Attack the advocate's case from multiple angles with severity ratings 3. **Judge Verdict** — Impartial assessment of advocate case vs critic attacks, rendering ACCEPT/REJECT/REVISE 4. **Iteration** (if REVISE) — Advocate revises case, critic re-attacks, judge re-evaluates
Available SOPs
| SOP | Role | Purpose | |-----|------|---------| | advocate-construction | Advocate | Build strongest case for position | | critic-attack | Critic | Attack the case with rated arguments | | judge-verdict | Judge | Render impartial verdict |
Execution Guidance
- Minimum 2 rounds before accepting ACCEPT verdict
- Critic must produce >= 3 distinct attack arguments per round
- Judge must address every critic argument explicitly
- If judge verdict is REVISE, advocate must address specific weaknesses identified
- Maximum 4 rounds before escalating to strategy level
Minimum Yield
- Advocate case with explicit evidence and reasoning
- Critic attacks with severity ratings (HIGH/MEDIUM/LOW)
- Judge verdict (ACCEPT/REJECT/REVISE) with point-by-point reasoning
- Conditions for acceptance (if ACCEPT)
- Required modifications (if REVISE)
<!-- BEGIN available-tables (generated) -->
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | advocate-construction | Construct the strongest possible case for a rejected candidate or counter-position. | | critic-attack | Attack an advocate's case with multiple arguments rated by severity. | | judge-verdict | Render an impartial verdict on advocate case vs critic attacks with explicit reasoning. |
<!-- END available-tables (generated) -->
Read more
name: adversarial-debate-protocol description: Structured debate protocol that constructs an advocate, deploys critic attacks, and renders a judge verdict through iterative rounds. execution: tactic dependencies: sops: - advocate-construction - critic-attack - judge-verdict
Adversarial Debate Protocol
A formal three-role debate structure ensuring decisions survive rigorous adversarial challenge. The protocol assigns distinct roles (advocate, critic, judge) to prevent confirmation bias and ensure intellectual honesty.
Stages
1. **Advocate Construction** — Build the strongest possible case for the position under debate 2. **Critic Attack** — Attack the advocate's case from multiple angles with severity ratings 3. **Judge Verdict** — Impartial assessment of advocate case vs critic attacks, rendering ACCEPT/REJECT/REVISE 4. **Iteration** (if REVISE) — Advocate revises case, critic re-attacks, judge re-evaluates
Available SOPs
| SOP | Role | Purpose | |-----|------|---------| | advocate-construction | Advocate | Build strongest case for position | | critic-attack | Critic | Attack the case with rated arguments | | judge-verdict | Judge | Render impartial verdict |
Execution Guidance
- Minimum 2 rounds before accepting ACCEPT verdict
- Critic must produce >= 3 distinct attack arguments per round
- Judge must address every critic argument explicitly
- If judge verdict is REVISE, advocate must address specific weaknesses identified
- Maximum 4 rounds before escalating to strategy level
Minimum Yield
- Advocate case with explicit evidence and reasoning
- Critic attacks with severity ratings (HIGH/MEDIUM/LOW)
- Judge verdict (ACCEPT/REJECT/REVISE) with point-by-point reasoning
- Conditions for acceptance (if ACCEPT)
- Required modifications (if REVISE)
<!-- BEGIN available-tables (generated) -->
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | advocate-construction | Construct the strongest possible case for a rejected candidate or counter-position. | | critic-attack | Attack an advocate's case with multiple arguments rated by severity. | | judge-verdict | Render an impartial verdict on advocate case vs critic attacks with explicit reasoning. |
<!-- END available-tables (generated) -->
The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.
Repo: yogsoth-ai/de-anthropocentric-research-engine
Other skills on de-anthropocentric-research-engine.
- /formated-results
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced block in your reply. Do not execute the research.
Open skill - /formated-specs
Spec-slot skill for the research-executor. Emit the 4-layer DARE orchestration of the assigned topic as one research-graph JSON fenced block in your reply. Replaces the generic spec-writing step.
Open skill - /injection-fidelity
Loss-1 judge (codex role). Given one sample's de-identified dialogue and its PolicyCard, decide axis-by-axis whether the user-simulator enacted the card's per-axis pressure. Judge enactment of the card, never whether the research is good.
Open skill - /ladder-quality-order
Loss-2 judge (codex role). Over one topic's 6 shuffled research-design samples, pairwise-rank by quality using the D1–D5 standard. Emit the pairwise log; the harness computes the order and the ladder verdicts. Judge quality difference, never against academic standards.
Open skill - /optimization-loop
The optimizer brain for the ladder-foundry pretraining loop. Runs the two-level nested batch loop, delegates gating to gate_eval, attributes a failing batch to one weight (attribute-first), and recovers from disk after compaction. Control flow is fully scripted; only the
Open skill - /acu-nugget-recall
Tactic: Extract atomic units from one paper and score how much of a caller-supplied summary covers. Use for ACU-style binary or Nugget-style ternary recall checks; cannot run without a target summary.
Open skill

