debate
Skill2 starsChanged 7 months agoMITView on GitHub
Explicit-only /debate round-table dispatcher for this repository. Use only when the user invokes /debate or when /room hands off a valid debate packet.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- bordenet/superpowers-plustheir own version, first seen Nov 13, 2026
- wolverin0/claude-skillstheir own version, first seen Nov 11, 2026
- Lu1sDV/skillsmdtheir own version, first seen Nov 4, 2026
- yoshibtc/multi-model-debate-skilltheir own version, first seen Oct 15, 2026
- phant0um/claude-skillstheir own version, first seen Oct 15, 2026
- helderberto/agent-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use handoff, commit and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 5 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- raine/consult-llm-mcp★ 148same name
- wolverin0/claude-skills★ 41same name
- helderberto/agent-skills★ 19same name
- ggombee/code-forge★ 18same name
- STRML/cc-debate★ 10same name
- bordenet/superpowers-plus★ 8same name
- Magnus-Gille/claude-skills★ 5same name
- agent-sh/debate★ 4same name
- HartreeWorks/research-skills★ 4same name
- ryancproduct/product-ai-toolkit★ 4same name
16 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms.txtllms.txt
- roomSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
If this file conflicts with those sources, follow those sources and report the mismatch.
- Distinctive: line 38
All protocols, schemas, and prompt specifications are fully contained within this repository.
- Distinctive: line 42
Use this skill only for explicit debate mode:
- Very specific: line 50
Do not use this skill for ordinary chat, /room exploration before upgrade, or single-agent advice.
- Very specific: line 54
Treat /debate as a round-table dispatcher and reviewer workflow, not as a personality.
- Distinctive: line 55
Do not let participants modify runtime state directly.
- Very specific: line 56
Keep /room handoff one-way through the packet contract.
- Very specific: line 57
Do not consume historical reports/ as current handoff input.
- Distinctive: line 58
Do not use old Windows paths as runtime entry points.
- Distinctive: line 60
Do not fabricate reviewer approval.
- Very specific: line 98
If the live wrapper reports claude_code_not_logged_in, do not mark the lane as passed.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/debate Project Skill Adapter
This is the Claude Code project-skill entry for /debate.
It is an adapter, not the canonical implementation source. The canonical /debate sources remain:
AGENTS.mddocs/protocol-spec.md.codex/skills/debate-roundtable-skill/SKILL.md.codex/skills/debate-roundtable-skill/runtime/README.mddocs/debate-runtime-bridge.mddocs/host-adapter-architecture.mddocs/debate-skill-architecture.mddocs/agent-role-map.mddocs/reviewer-protocol.mddocs/decision-quality-rubric.mddocs/red-flags.mddocs/room-to-debate-handoff.mdschemas/debate-session.schema.jsonschemas/debate-result.schema.jsonschemas/room-to-debate-handoff.schema.jsonprompts/debate-roundtable.mdprompts/debate-reviewer.mdprompts/debate-followup.md
If this file conflicts with those sources, follow those sources and report the mismatch.
Self-Contained Path Resolution & Fallback
This skill adapter is 100% self-contained and portable:
- Primary path resolution uses repo-relative paths (e.g.
docs/...,prompts/...,schemas/...). - Canonical absolute path fallback: When running outside the repository root or in global host contexts, resolve all referenced files against
/Users/markdonish/round-table-workspace/(e.g./Users/markdonish/round-table-workspace/docs/protocol-spec.md). - All protocols, schemas, and prompt specifications are fully contained within this repository.
Trigger Boundary
Use this skill only for explicit debate mode:
/debate <topic>/debate --with ... <topic>/debate --without ... <topic>/debate --quick <topic>- a valid
/roomhandoff packet accepted by the checked-in packet preflight
Do not use this skill for ordinary chat, /room exploration before upgrade, or single-agent advice.
Operating Rules
- Treat
/debateas a round-table dispatcher and reviewer workflow, not as a personality. - Do not let participants modify runtime state directly.
- Keep
/roomhandoff one-way through the packet contract. - Do not consume historical
reports/as current handoff input. - Do not use old Windows paths as runtime entry points.
- Separate facts, inferences, uncertainty, and recommendations.
- Do not fabricate reviewer approval. If review fails, return a blocked or follow-up state.
Runtime Entry Points
For deterministic validation:
python3 .codex/skills/debate-roundtable-skill/runtime/debate_e2e_validation.py \
--executor fixture \
--scenario reject_followup \
--state-root /tmp/round-table-debate-e2e-followupFor Claude Code adapter-route validation without a Claude subscription:
python3 .codex/skills/room-skill/runtime/room_debate_e2e_validation.py \
--executor claude_code \
--agent-command "python3 .codex/skills/room-skill/runtime/generic_fixture_agent.py" \
--scenario reject_followup \
--state-root /tmp/round-table-claude-code-adapter-fixtureFor real Claude Code host-live validation, only if the local Claude Code account is entitled:
python3 .codex/skills/room-skill/runtime/claude_code_live_validation.py \
--preflight-only \
--state-root /tmp/round-table-claude-code-live-preflight
python3 .codex/skills/room-skill/runtime/claude_code_live_validation.py \
--smoke-only \
--state-root /tmp/round-table-claude-code-live-smoke
python3 .codex/skills/room-skill/runtime/claude_code_live_validation.py \
--state-root /tmp/round-table-claude-code-liveIf the live wrapper reports claude_code_not_logged_in, do not mark the lane as passed. A --smoke-only pass proves local CLI execution only; claim the default Claude Code lane only when the full wrapper reports claimable_as_default_claude_code_host_live=true.
<!-- rtw:generated-skill-summary:start -->Generated Skill Summary
- Skill id:
debate - Source schema:
0.1.0 - Entry commands:
/debate <topic>,/debate --with Jobs,Taleb <topic>,/debate --quick <topic> - Shared rules:
explicit-only,local-first,claim-safe,do-not-use-reports-as-source,do-not-claim-fixture-as-live,cognitive-lens-not-voice-imitation - Claim boundary: fixture/checker passes are not host-live and not provider-live evidence.
Canonical refs:
AGENTS.mddocs/protocol-spec.mddocs/debate-skill-architecture.mddocs/reviewer-protocol.mddocs/decision-quality-rubric.mddocs/room-to-debate-handoff.mdschemas/debate-session.schema.jsonschemas/debate-result.schema.jsonschemas/room-to-debate-handoff.schema.jsonprompts/debate-roundtable.mdprompts/debate-reviewer.mdprompts/debate-followup.md
Host-specific notes:
codex: Canonical checked-in debate runtime and skill entrypoint.claude: Project-skill adapter that points back to canonical Codex/docs sources.
<!-- rtw:generated-skill-summary:end -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

