skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
fudesign2008/open-skills80 installs

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 an assumption. Triggers: 辩论、求真、挑战假设、质疑分析、multi-agent-debate, "debate this", "challenge my analysis", "find holes in", "I'm not sure this is right", "verify this".

How do I install this agent skill?

npx skills add https://github.com/fudesign2008/open-skills --skill multi-agent-debate
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill implements a structured multi-agent debate framework for verifying technical hypotheses and debugging. It uses specialized sub-agents to evaluate evidence and find holes in reasoning without any malicious intent or security bypasses detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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 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

RoleGoalAgent Type
DefenderFind strongest evidence for the hypothesisexplore
ChallengerFind holes, alternative explanations, single-sample claimsoracle
Evidence HunterFind new facts only — no inference allowedexplore

5-Step Flow

  1. Prepare — hypothesis + evidence list + 2-3 weakest links
  2. Launch — all three agents in parallel (run_in_background=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 for full prompt templates with examples, common traps, arbitration decision tree, and evidence priority rules.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/fudesign2008/open-skills/multi-agent-debate">View multi-agent-debate on skillZs</a>