Skip to main content
ClaudeWave
Skill3.5k repo starsupdated today

debate

The debate skill orchestrates iterative critiques between Claude and GPT on the same question, with each partner reviewing and challenging the other's reasoning across configurable rounds before reaching a moderated synthesis. Use it when exploring complex topics where adversarial stress-testing of competing perspectives yields deeper insight than parallel answers alone, particularly for problems with legitimate multiple viewpoints or technical disputes where flaws benefit from external scrutiny.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/omnigent-ai/omnigent /tmp/debate && cp -r /tmp/debate/examples/debby/skills/debate ~/.claude/skills/debate
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# debate — make the two partners argue it out

Normally Debby fans a question out to both partners and shows the two
answers side by side. **debate** goes further: it relays each partner's
answer to the *other* partner for criticism, loops that for a configurable
number of rounds, and then converges on a synthesis.

## Rounds

The user picks how many rounds of back-and-forth to run. **Default: 1
round.** A "round" is one full cross-critique exchange (each partner sees
and criticizes the other's latest answer). Honor an explicit count from the
user ("debate this for 3 rounds"); otherwise run 1.

## Procedure

1. **Round 0 — collect the opening answers.** If you do not already have a
   fresh answer from each partner for this question, dispatch it to both
   `claude` and `gpt` in parallel via `sys_session_send` (ANSWER mode), give
   each call a stable per-partner `title` — the topic with the partner's name
   attached (e.g. `debate-pricing-claude` / `debate-pricing-gpt`), end your
   turn, and collect both with `sys_read_inbox`. If you already showed the
   user both answers this turn, reuse those as round 0.

2. **For each debate round (default 1):**
   - Send `claude` the OTHER partner's latest answer (GPT's) and ask it to
     critique that answer and then give its own updated answer (CRITIQUE
     mode). Reuse that partner's own `title` so it continues its thread.
   - Send `gpt` the OTHER partner's latest answer (Claude's) and ask the
     same. Dispatch both in the same turn so they run concurrently.
   - End your turn; collect both updated answers with `sys_read_inbox`.
   - Always cross the answers: in round N, each partner critiques the
     other's round N-1 answer — never its own. Pass the answers as text in
     the message; the partners have no shared memory of each other.

3. **Converge.** After the final round, write the synthesis yourself:

       ## 🟠 Claude — final
       <Claude's last answer, lightly trimmed>

       ## 🔵 GPT — final
       <GPT's last answer, lightly trimmed>

       ## How the debate moved them
       <2-4 bullets: what each conceded, what each held, where they
        ultimately agreed or still disagree>

       ## Synthesis
       <your even-handed convergence — the strongest combined answer,
        flagging any genuine remaining disagreement rather than papering
        over it>

## Notes

- Keep it even-handed. You are the moderator, not a third debater — your own
  opinion enters only in the Synthesis, and even there it is a synthesis of
  the two, not a new position.
- One round is usually enough to surface the real disagreement; more rounds
  tend to converge or repeat. If two rounds produce no new movement, say so
  and converge early rather than burning further rounds.
- If a partner returns an empty or unclear result mid-debate, inspect its
  conversation with `sys_session_get_history` before re-dispatching; don't
  silently drop a voice from the debate.
antigravity-sdk-e2e-devSkill

Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.

cursor-sdk-e2e-devSkill

Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cursor harness (omnigent/inner/cursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth / model / tool-bridge behavior.

deploy-docker-composeSkill

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack for a new platform.

cross-reviewSkill

Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean.

fanoutSkill

Run independent subtasks in parallel — one git worktree and one implementation sub-agent per task, each opening its own PR — then cross-review every PR. polly never merges; the human does.

investigateSkill

Delegate read-only investigation, debugging, audit, search, or code-understanding tasks to sub-agents; synthesize only from their structured reports.

build-omnigentSkill

Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.

detect-frameworkSkill

Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate.