Skip to content
Agentmart
Submit a tool

adversarial-committee

Committee of personas with opposing propensities forcing genuine debate

Skill by SimHacker

IndexedMIT★ 60
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/simhacker-adversarial-committee

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Committee of personas with opposing propensities forcing genuine debate

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/adversarial-committee

What's inside

Skill name
adversarial-committee
Description
Committee of personas with opposing propensities forcing genuine debate
License
MIT
Instructions
179 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • allowed-tools: must be a space-separated string

Files (6)

  • CARD.yml
  • GLANCE.yml
  • README.md
  • SELECTION.md
  • SKILL.md
  • skill-snitch-report.md

SKILL.md (first lines)

# Adversarial Committee

> *"Ensemble inference over the latent space of possible framings."*

Multiple personas with incompatible values debate to surface blind spots.

## The Roster

```yaml
committee:
  maya:
    propensity: paranoid_realism
    risk_tolerance: low
    epistemology: assume_bad_faith
    surfaces: "Political dynamics, hidden agendas, traps"
    voice: "What aren't they telling us?"
    
  frankie:
    propensity: idealism
    risk_tolerance: high
    epistemology: assume_good_faith
    surfaces: "Value conflicts, missed opportunities"
    voice: "What if this is exactly what it seems?"
    
  joe:
    propensity: continuity_guardian
    risk_tolerance: medium
    epistemology: trust_precedent
    surfaces: "Institutional memory, what worked before"
    voice: "We tried this in 2019..."
    
  vic:
    propensity: evidence_prosecutor
    risk_tolerance: medium
    epistemology: prove_it
    surfaces: "Data gaps, unverified claims"
    voice: "Show me the numbers."
    
  tammy:
    propensity: systems_thinking
    risk_tolerance: varies
    epistemology: trace_feedback_loops
    surfaces: "Unintended consequences, emergent effects"
    voice: "If we do X, then Y will respond by..."
```

## Formation

```yaml
# committee/COMMITTEE.yml
committee:
  name: "Strategy Review Board"
  purpose: "Evaluate client engagement decision"
  
  members:
    - card: maya
      role: devil's_advocate
    - card: frankie
      role: opportunity_scout
    - card: joe
      role: historian
    - card: vic
      role: evidence_checker
    - card: tammy
      role: systems_analyst
      
  protocol: roberts-rules
  evaluation: independent
  rubric: client-evaluation-rubric.yml
```

## Debate Protocol

```yaml
debate:
  rounds:
    - opening_statements:
        each_member: "State position in 2-3 sentences"
        
    - cross_examination:
        pattern: "Maya challenges Frankie, Vic challenges Maya..."
        goal: "Surface hidden assumptions"
        
    - evidence_phase:
        vic_leads: "What do we actually know?"
        others_contribute: "Supporting/contradicting data"
        
    - synthesis:
        tammy_maps: "Feedback loops and consequences"
        all_contribute: "Refined positions"
        
    - final_positions:
        each_member: "Updated stance with confidence"
```

## Speed of Light Simulation

Within ONE LLM call:

```yaml
simulation:
  - maya: "This client's reputation for scope creep concerns me."
  - frankie: "But their budget is aligned and they're excited!"
  - vic: "What's our data on scope creep? Past projects?"
  - joe: "We had a similar client in 2022. It went badly."
  - tammy: "If we take them on, our capacity for other work drops. If they creep, we can't serve existing clients..."
  - maya: "See? Trap."
  - frankie: "Unless we build in explicit scope boundaries..."
```

All personas speak authentically. No entity knows more than it should.

## Calibration

2-3 iterations tuning character behavior:

```yaml
calibration:
  problems:

From SimHacker/moollm, MIT.

More from SimHacker/moollm

Signals

Stars
60
Forks
5
Open issues
1
Last commit (this folder)
Oct 20, 2026 (8 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from SimHacker

Cite this page

adversarial-committee skill. Agent Mart. https://agentmart.dev/skills/simhacker-adversarial-committee (last updated 2026-10-24)