跳到正文
cccskills
免费在 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.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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.

查看安装方法

适用场景

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

包含的文件(1)

  • SKILL.md3.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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/omnigent1.1万2026年10月21日 更新

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/omnigent1.1万2026年10月21日 更新

api-docs

免费

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/omnigent1.1万2026年10月21日 更新

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/omnigent1.1万2026年10月21日 更新

changelog

免费

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/omnigent1.1万2026年10月21日 更新

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/omnigent1.1万2026年10月21日 更新

查看 omnigent-ai 的全部技能

报告此技能的问题