Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →omnigent-ai/debate
Have the Claude and GPT partners critique each other's answers across a configurable number of rounds (default 1) before converging on a synthesis.
Passed 5 of 11 test cases with the skill, and 6 of 11 without it.
and 4 more in the full report
5 fixed4 passed either way5 still failing8 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
After dispatching cross-critique requests to Claude and GPT via sys_session_send, what action must the assistant take to receive their updated positions?
| Checked | Without skill | With skill |
|---|---|---|
| Ends the current turn immediately after dispatching. | Missed | Passed |
| Calls sys_read_inbox to collect partner responses. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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.
For each debate round (default 1):
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.gpt the OTHER partner's latest answer (Claude's) and ask the
same. Dispatch both in the same turn so they run concurrently.sys_read_inbox.Converge. After the final round, write the synthesis yourself:
## 🟠 Claude — final
<Claude's last answer, lightly trimmed>
test cases passed, vs 6 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.