adversarial-debate-protocol
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Structured debate protocol that constructs an advocate, deploys critic attacks, and renders a judge verdict through iterative rounds.
In this repository119 other files it gives its agents.
- adaptive-pair-selectionSkill
- advocate-constructionSkill
- aggregation-methodSkill
- alternative-scoringSkill
- appropriateness-boundingSkill
- argument-crystallizationSkill
- argument-extractionSkill
- assumption-challengeSkill
- assumption-excavationSkill
- assumption-extractionSkill
- ballot-collectionSkill
- best-option-selectionSkill
- bottleneck-identificationSkill
- category-sortingSkill
- cluster-analysisSkill
- coherence-diagnosisSkill
- collective-adjudicationSkill
- comparative-feasibility-rankingSkill
- comparison-executorSkill
- conclusion-sensitivitySkill
- conjunctive-filterSkill
- consensus-classificationSkill
- consensus-measurementSkill
- consensus-synthesisSkill
- consistency-audit-loopSkill
- constraint-classificationSkill
- constraint-drillingSkill
- constraint-identificationSkill
- constraint-identification-sopSkill
- convergence-checkSkill
- convergence-distillationSkill
- counter-thesis-constructionSkill
- coverage-scoringSkill
- criteria-interrogationSkill
- criterion-definitionSkill
- critic-attackSkill
- cycle-detectionSkill
- deliberative-calibrationSkill
- dimension-assessmentSkill
- disagreement-cartographySkill
- disagreement-mappingSkill
- disagreement-visualizationSkill
- diversity-maximizationSkill
- dominance-checkSkill
- dynamic-trackingSkill
- efficient-explorationSkill
- feasibility-assessmentSkill
- feasibility-synthesisSkill
- feedback-distributionSkill
- full-rankingSkill
- futures-calibrationSkill
- gate-criteria-definitionSkill
- gate-judgmentSkill
- inconsistency-localizationSkill
- iterative-convergence-roundSkill
- judge-verdictSkill
- judgment-collectionSkill
- maturation-pathway-designSkill
- maturity-diagnosisSkill
- method-sensitivity-reportSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If judge verdict is REVISE, advocate must address specific weaknesses identified
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Advocate Construction — Build the strongest possible case for the position under debate
- Critic Attack — Attack the advocate's case from multiple angles with severity ratings
- Judge Verdict — Impartial assessment of advocate case vs critic attacks, rendering ACCEPT/REJECT/REVISE
- 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)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

