fudesign2008/open-skills

multi-agent-debate

Stress-test a crash analysis, hypothesis, or technical conclusion by launching three adversarial agents in parallel — one defends, one attacks, one hunts new evidence — and resolving disputes with physical proof instead of argument. Always use this skill when the analysis has 2+ competing explanations that both seem plausible, when a conclusion relies on a single log sample or inferred chain longer than 3 steps, or when someone says \"are you sure?\", \"that doesn't sound right\", or challenges…

First seen Jun 25, 2026

Installation

$ npx skills add fudesign2008/open-skills --skill multi-agent-debate

Summary

  • Stress-test a crash analysis, hypothesis, or technical conclusion by launching three adversarial agents in parallel — one defends, one attacks, one hunts new evidence — and resolving disputes with physical proof instead of argument.
  • Always use this skill when the analysis has 2+ competing explanations that both seem plausible, when a conclusion relies on a single log sample or inferred chain longer than 3 steps, or when someone says \"are you sure?\", \"that doesn't sound right\", or challenges an assumption.
  • Triggers: 辩论、求真、挑战假设、质疑分析、multi-agent-debate, \"debate this\", \"challenge my analysis\", \"find holes in\", \"I'm not sure this is right\", \"verify this\".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from fudesign2008/open-skills · top by installs.

npx skills add fudesign2008/open-skills

Browse all from fudesign2008/open-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,768 B
  • docs SUMMARY.md 734 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 57 installs

SKILL.md

Multi-Agent Debate

Core rule: Reasoning disputes cannot be resolved by more reasoning. Only evidence arbitrates.

Quick Start

  1. Write your hypothesis in one paragraph
  2. List existing evidence (each with source: file, line, or command)
  3. Identify 2–3 weakest links in your analysis
  4. Fill in the three prompts below and launch in parallel
task(subagent_type="explore",  run_in_background=true, prompt="[DEFENDER]...")
task(subagent_type="oracle",   run_in_background=true, prompt="[CHALLENGER]...")
task(subagent_type="explore",  run_in_background=true, prompt="[EVIDENCE HUNTER]...")

Why separate prompts? Each agent must be blind to the others' goals — if the Challenger sees the Defender's framing, it anchors on the same assumptions it's supposed to attack. Fill in each prompt from [REFERENCE.md](REFERENCE.md) independently.

Minimal prompt structure (fill in <...>):

DEFENDER:   "You are the DEFENDER for: <hypothesis>. Find direct physical evidence
             (file:line, command output, code) for each claim. List the 3 weakest
             points and collect pre-emptive counter-evidence."

CHALLENGER: "You are the CHALLENGER for: <hypothesis>. Find holes: alternative
             explanations, single-sample claims, inferences used as facts. For
             every alternative you propose, provide how to falsify it."

HUNTER:     "Find facts only — no inference. Answer: <2-3 specific questions from
             disputed claims>. Every answer must be a command output or code verbatim.
             Tag each: [SUPPORTS] / [CHALLENGES] / [NEUTRAL]."

Three Roles

Role Goal Agent Type
Defender Find strongest evidence for the hypothesis explore
Challenger Find holes, alternative explanations, single-sample claims oracle
Evidence Hunter Find new facts only — no inference allowed explore

5-Step Flow

  1. Prepare — hypothesis + evidence list + 2-3 weakest links
  2. Launch — all three agents in parallel (runinbackground=true)
  3. Triage — split results into: agreed facts / disputed claims / new evidence
  4. Arbitrate — for each dispute, find a command/file/code that directly resolves it; if only reasoning exists, mark [UNRESOLVED]
  5. Conclude — write only what has physical evidence; disputed items stay pending

Conclusion Format

### Confirmed Facts [FACT:source]
### Reasonable Inferences [INFERENCE]
### Unresolved Disputes — verification method needed
### Corrected Mistakes — original → corrected | evidence

Evidence Tags

[FACT:file:line] · [FACT:cmd] · [FACT:N samples] · [INFERENCE] · [SPECULATION] · [UNRESOLVED]

No bare claims in conclusions. Every statement needs a tag.


See [REFERENCE.md](REFERENCE.md) for full prompt templates with examples, common traps, arbitration decision tree, and evidence priority rules.