Skip to content
cccskills
FreePublished on GitHub

debate

Have Claude and GPT critique each other's answers, revise their positions, and work toward a combined response. Choose the number of rounds and see what changed, where they agree, and which disagreements remain.

OriginalShow the original description

Have the Claude and GPT partners critique each other's answers across a configurable number of rounds (default 1) before converging on a synthesis. Use when the user wants the two perspectives stress-tested against each other, not just shown side by side.

See how to install

Good for

  • Stress-testing a proposal from two perspectives
  • Finding weaknesses in competing answers
  • Combining agreement while preserving unresolved differences

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.

  • Testing message delivery from the web interface to agy
  • Checking terminal output against mirrored session replies
  • Verifying permission requests and interruption
omnigent-ai/omnigent10.9KUpdated Oct 19, 2026

Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.

  • Test authentication and real Gemini responses
  • Verify tool connections and sub-agent delegation
  • Investigate model selection failures
omnigent-ai/omnigent10.9KUpdated Oct 19, 2026

api-docs

FreeSummary

Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.

  • Writing reference docs for a public module
  • Documenting command-line arguments and defaults
  • Adding minimal usage examples for an API
omnigent-ai/omnigent10.9KUpdated Oct 19, 2026

build-omnigent

FreeSummary

Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.

  • Creating a minimal Omnigent agent
  • Configuring an agent with web search
  • Adding shell access or MCP tool connections
omnigent-ai/omnigent10.9KUpdated Oct 19, 2026

changelog

FreeSummary

Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.

  • Write release notes covering changes since the last tag
  • Summarize pull requests merged during a selected period
  • Highlight breaking changes before an upgrade
omnigent-ai/omnigent10.9KUpdated Oct 19, 2026

cli-setup-verify

FreeSummary

Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.

  • Reproducing a first-run setup problem
  • Inspecting menus in a narrow terminal
  • Checking help text and command visibility
omnigent-ai/omnigent10.9KUpdated Oct 19, 2026

See all skills by omnigent-ai

Report a problem with this skill