adversarial-deliberation
Skill505 starsChanged 49 days agoApache-2.0View on GitHub
Run structured attack/defense/adjudication over a claim, candidate, criterion set, or current winner. Perspective, target, escalation depth, loser-resurrection, and steelman/winner-stress modes are parameters; role execution is runtime-agnostic.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- usecompai/compound-operations-modeltheir own version, first seen Nov 8, 2026
- Pthahnix/De-Anthropocentric-Research-Engineword for word, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Pthahnix/De-Anthropocentric-Research-Engine★ 504100% same
Edited · 0
None found.
Wrote their own version · 1
- usecompai/compound-operations-model★ 31same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository270 other files it gives its agents.
- abstract-structureSkill
- adjudicate-exchangeSkill
- adjust-abstraction-scopeSkill
- aggregate-rankingSkill
- analogical-discoverySkill
- analyze-constraints-readinessSkill
- analyze-experiment-resultsSkill
- analyze-future-scenariosSkill
- analyze-heterogeneitySkill
- analyze-interventionSkill
- analyze-leaderboard-dynamicsSkill
- analyze-patent-citation-networkSkill
- analyze-scaling-regimeSkill
- analyze-temporal-trajectorySkill
- apply-perturbationSkill
- apply-question-frameworkSkill
- apply-separation-principleSkill
- apply-stage-gateSkill
- apply-veto-filterSkill
- appreciative-reframeSkill
- assess-construct-validitySkill
- assess-evidence-saturationSkill
- assess-goal-feasibilitySkill
- assess-patent-claim-scopeSkill
- assess-patent-legal-statusSkill
- assess-prior-art-and-claimsSkill
- assess-problem-wickednessSkill
- assess-publication-biasSkill
- assess-question-qualitySkill
- assess-ranking-consistencySkill
- assess-readiness-dimensionSkill
- assess-removabilitySkill
- assess-sensitivitySkill
- assess-system-boundarySkill
- assumption-stress-testSkill
- atomize-claimSkill
- atomize-conceptSkill
- attach-evidence-to-relationSkill
- audit-benchmark-validitySkill
- audit-convergence-independenceSkill
- audit-data-contaminationSkill
- audit-explanatory-compressionSkill
- audit-reporting-qualitySkill
- audit-structural-equivalenceSkill
- audit-structure-consistencySkill
- audit-study-validitySkill
- audit-validator-independenceSkill
- biologize-problemSkill
- biomimetic-transferSkill
- build-concept-fanSkill
- build-current-reality-treeSkill
- build-domain-ontologySkill
- build-failure-chainSkill
- build-noncircularity-matrixSkill
- calibrate-adversarial-confidenceSkill
- calibrate-probability-forecastSkill
- canonicalize-entitySkill
- categorize-evidenceSkill
- challenge-assumptionSkill
- characterize-anomalySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run structured attack, defense, cross-examination, and adjudication over a claim, candidate, criterion set, or current winner.
- Distinctive: line 24
Do not perform called SOP operations inline.
- Very specific: line 30
If the task shifts from balanced exchange to direct attack-surface probing, consider structured-red-team.
- Distinctive: line 53
Every verdict must cite criteria and preserve dissent.
- Distinctive: line 55
Do not treat rhetorical fluency as evidence.
≈ “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-deliberation
Purpose
Run structured attack, defense, cross-examination, and adjudication over a claim, candidate, criterion set, or current winner.
Input contract
mode_contracts:
critic-defender-judge: &deliberation_input
required: [target, claim_or_candidate, criteria]
optional: [perspectives, escalation_depth]
constraints: [target_scope_and_criteria_must_be_explicit, evidence_provenance_required]
courtroom: *deliberation_input
winner-stress: *deliberation_input
resurrection-advocacy: *deliberation_input
criteria-interrogation: *deliberation_input
stakeholder-objection: *deliberation_input
counter-thesis: *deliberation_inputExecution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.
- You MUST load skill
construct-critiqueto construct the strongest attack. You MUST load skillconstruct-defenseto construct the strongest defensible case. - You MUST load skill
surface-assumptionsto expose load-bearing assumptions. You MUST load skillconstruct-perspective-setto construct alternate perspectives. - You MUST load skill
cross-examineto cross-examine each exchange. You MUST load skillassess-sensitivityto perturb load-bearing choices. - You MUST load skill
adjudicate-exchangeto adjudicate against declared criteria. You MUST load skillcalibrate-adversarial-confidenceto update calibrated confidence. If the task shifts from balanced exchange to direct attack-surface probing, considerstructured-red-team. If an exposed assumption requires focused perturbation, considerassumption-stress-test. If the surviving claim needs a decisive falsification program,falsification-first-auditmay be the better next tactic. Deviation: skip defense only when the target is explicitly exploratory; skip sensitivity only when no perturbable input is declared; otherwise retain all steps.
Output contract
mode_contracts:
critic-defender-judge: &full_deliberation_output
produces: [attack_record, defense_record, adjudication, confidence_trace]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
courtroom: *full_deliberation_output
winner-stress:
produces: [attack_record, adjudication, confidence_trace]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
resurrection-advocacy: &defense_deliberation_output
produces: [defense_record, adjudication, confidence_trace]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
criteria-interrogation:
produces: [attack_record, defense_record, adjudication]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
stakeholder-objection: *full_deliberation_output
counter-thesis: *defense_deliberation_outputThresholds and quality gates
- A-class debate calibration: declared universe = all rounds and claims; numerator = rounds with evidence-linked confidence updates; batch increment = one completed exchange; stopping reason = confidence stabilizes or unresolved disagreement is explicitly reported; source references = evidence IDs and round IDs; direction/threshold reason = escalate when new evidence changes ranking, terminate only when criteria are adjudicated or a non-resolvable uncertainty is recorded.
- Every verdict must cite criteria and preserve dissent.
Failure and counterexamples
Do not treat rhetorical fluency as evidence. Mark unresolved when attack and defense share an untested assumption or criteria are absent.
Provenance map
- resolved: multiagent-debate
- resolved: critic-defender-judge
- resolved: courtroom-structured
- resolved: adversarial-escalation
- resolved: steel-manning
- resolved: resurrection-advocacy
- resolved: winner-stress-testing
- resolved: adversarial-debate-protocol
- resolved: assumption-excavation
- resolved: multi-perspective-attack
- intermediate: Pass5/adversarial-debate
- intermediate: Pass5/steelman-validation
Preserved source criteria ledger
| source | source line | kind | source criterion |
| v4 architecture | node desc | textual | Structured attack/defense/adjudication; loser-resurrection and steelman/winner-stress are parameters. |
Context checkpoint / Delta notes
Append claim, criteria, attack/defense records, dissent, confidence changes, and unresolved questions.
Mode branches
critic-defender-judge: attack, defense, adjudication.courtroom: add cross-examination and explicit evidentiary ruling.winner-stress: perturb the current winner and record failure triggers.resurrection-advocacy: re-open a rejected candidate with a steelman.criteria-interrogation: challenge the criteria before ranking.stakeholder-objection: add perspective-specific objections.counter-thesis: require a mechanism-distinct opposing thesis.
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.

