agentleFS
MihirokteMihirokte/agent-skills/skills/debate/SKILL.md

debate

Skill0 starsChanged 4 months agoMITView on GitHub

Runs a multi-agent code debate through the separately installed Debate Hall application. Use when the user invokes /debate with a repository path.

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

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user sends /debate <directory>:

    line 19
  2. Distinctive:

    Treat Debate Hall as read-only review tooling unless the user explicitly requests implementation afterward.

    line 36
  3. Very specific:

    Do not vendor debate.py, Hall UI assets, or runtime files into this skill.

    line 38
  4. Very specific:

    Add .debate/ to the reviewed repository's .gitignore when the user does not want run artifacts committed.

    line 39

“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

This skill is a thin integration. The Debate Hall runtime is deliberately not copied into this repository.

Prerequisite

The debate-run command must be installed and available on PATH. If it is missing, tell the user to install the standalone debate-app package; do not reimplement or copy its runtime into the skills directory.

Run

When the user sends /debate <directory>:

  1. Resolve and validate the directory.
  2. Confirm debate-run is available.
  3. Run:

    debate-run "<directory>"
  4. Report where the generated .debate/ artifacts were written.

For a persistent UI, run debate-hall and direct the user to the URL printed by the application.

Safety

  • Treat Debate Hall as read-only review tooling unless the user explicitly requests implementation afterward.
  • Do not vendor debate.py, Hall UI assets, or runtime files into this skill.
  • Add .debate/ to the reviewed repository's .gitignore when the user does not want run artifacts committed.

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.