agentleFS
MarkDonishMarkDonish/round-table-workspace/.claude/skills/debate/SKILL.md

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

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.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • SentrySkill

    commit

    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

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

  • SentrySkill

    skill-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

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
  1. Distinctive:

    If this file conflicts with those sources, follow those sources and report the mismatch.

    line 31
  2. Distinctive:

    All protocols, schemas, and prompt specifications are fully contained within this repository.

    line 38
  3. Distinctive:

    Use this skill only for explicit debate mode:

    line 42
  4. Very specific:

    Do not use this skill for ordinary chat, /room exploration before upgrade, or single-agent advice.

    line 50
  5. Very specific:

    Treat /debate as a round-table dispatcher and reviewer workflow, not as a personality.

    line 54
  6. Distinctive:

    Do not let participants modify runtime state directly.

    line 55
  7. Very specific:

    Keep /room handoff one-way through the packet contract.

    line 56
  8. Very specific:

    Do not consume historical reports/ as current handoff input.

    line 57
  9. Distinctive:

    Do not use old Windows paths as runtime entry points.

    line 58
  10. Distinctive:

    Do not fabricate reviewer approval.

    line 60
  11. Very specific:

    If the live wrapper reports claude_code_not_logged_in, do not mark the lane as passed.

    line 98

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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.md
  • docs/protocol-spec.md
  • .codex/skills/debate-roundtable-skill/SKILL.md
  • .codex/skills/debate-roundtable-skill/runtime/README.md
  • docs/debate-runtime-bridge.md
  • docs/host-adapter-architecture.md
  • docs/debate-skill-architecture.md
  • docs/agent-role-map.md
  • docs/reviewer-protocol.md
  • docs/decision-quality-rubric.md
  • docs/red-flags.md
  • docs/room-to-debate-handoff.md
  • schemas/debate-session.schema.json
  • schemas/debate-result.schema.json
  • schemas/room-to-debate-handoff.schema.json
  • prompts/debate-roundtable.md
  • prompts/debate-reviewer.md
  • prompts/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 /room handoff 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

  1. Treat /debate as a round-table dispatcher and reviewer workflow, not as a personality.
  2. Do not let participants modify runtime state directly.
  3. Keep /room handoff one-way through the packet contract.
  4. Do not consume historical reports/ as current handoff input.
  5. Do not use old Windows paths as runtime entry points.
  6. Separate facts, inferences, uncertainty, and recommendations.
  7. 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-followup

For 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-fixture

For 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-live

If 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.md
  • docs/protocol-spec.md
  • docs/debate-skill-architecture.md
  • docs/reviewer-protocol.md
  • docs/decision-quality-rubric.md
  • docs/room-to-debate-handoff.md
  • schemas/debate-session.schema.json
  • schemas/debate-result.schema.json
  • schemas/room-to-debate-handoff.schema.json
  • prompts/debate-roundtable.md
  • prompts/debate-reviewer.md
  • prompts/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 -->

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.