Debate
Compare Claude and GPT answers through rounds of mutual critique before synthesizing.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/debate-omnigent-ai/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
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.
What this skill does
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
-
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
claudeandgptin parallel viasys_session_send(ANSWER mode), give each call a stable per-partnertitle— the topic with the partner's name attached (e.g.debate-pricing-claude/debate-pricing-gpt), end your turn, and collect both withsys_read_inbox. If you already showed the user both answers this turn, reuse those as round 0. -
For each debate round (default 1):
- Send
claudethe 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 owntitleso it continues its thread. - Send
gptthe 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.
- Send
-
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_historybefore re-dispatching; don't silently drop a voice from the debate.
Related skills
App Store Listing Audit
coreyhaines31
Analyze your app listing against best practices and get a prioritized optimization plan.
Co-Marketing Partnerships
coreyhaines31
Find ideal partners and plan joint marketing campaigns with other companies.
Cold Email Writer
coreyhaines31
Write B2B cold emails and follow-up sequences designed to get replies.
Community-Led Growth
coreyhaines31
Build and grow online communities to drive product adoption and customer loyalty.