Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers.
Install Argue
$ npx skills add onevcat/argue --skill argue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install onevcat/argue argue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/onevcat/argue.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/argue .claude/skills/argue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "argue" agent skill from https://github.com/onevcat/argue/tree/master/skills/argue into .claude/skills/argue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "argue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/onevcat/argue/tree/master/skills/argueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add onevcat/argue --skill argue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install onevcat/argue argue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onevcat/argue.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/argue .agents/skills/argue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "argue" agent skill from https://github.com/onevcat/argue/tree/master/skills/argue into .agents/skills/argue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "argue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add onevcat/argue --skill argue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install onevcat/argue argue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onevcat/argue.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/argue .cursor/skills/argue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "argue" agent skill from https://github.com/onevcat/argue/tree/master/skills/argue into .cursor/skills/argue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "argue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/onevcat/argue.git --path skills/argue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add onevcat/argue --skill argue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install onevcat/argue argue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onevcat/argue.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/argue .gemini/skills/argue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "argue" agent skill from https://github.com/onevcat/argue/tree/master/skills/argue into .gemini/skills/argue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "argue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install onevcat/argue argueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add onevcat/argue --skill argue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/onevcat/argue.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/argue .github/skills/argue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "argue" agent skill from https://github.com/onevcat/argue/tree/master/skills/argue into .github/skills/argue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "argue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add onevcat/argue --skill argue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install onevcat/argue argue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onevcat/argue.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/argue .opencode/skills/argue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "argue" agent skill from https://github.com/onevcat/argue/tree/master/skills/argue into .opencode/skills/argue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "argue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
argue- GitHub stars
- 279
- Token cost
- ~1.9k tokens
- SKILL.md length
- 580 words
- Files
- 3 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers.
- Works in 4 steps: Frame as decisions, not topics. "Should… → Add context. "Should we use a monorepo?… → 2–3 agents is the sweet spot. Agents in… → …
- Facing strategic decisions
- SKILL.md covers When to Use, Pre-flight, Running Debates and Viewing & Acting on Results, plus 3 more sections
- Calls npm
What it does
Argue is an agent skill from onevcat/argue. Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers. Use when facing strategic decisions, ambiguous trade-offs, architecture debates, or questions where multiple perspectives improve the answer. Triggers on: argue, debate, cross-examine, second opinion, multi-agent, 'Should we X or Y?' with real stakes, consensus-building, risk analysis, or confirmation-bias mitigation.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/setup.md` and `references/troubleshooting.md`). Compatibility notes: Requires argue CLI (@onevcat/argue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini…
It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Harness-agnostic orchestration package for multi-agent consensus workflows. The licence is MIT.
When your agent uses it
- Facing strategic decisions
- Ambiguous trade-offs
- Architecture debates
- Questions where multiple perspectives improve the answer
Example prompts
- “Should we X or Y?”
- “/argue”
Requirements
- Node.js
- Compatibility (from SKILL.md): Requires argue CLI (@onevcat/argue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini, claude, etc.). API-based providers need API keys in environment.
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Frame as decisions, not topics. "Should we use SwiftUI or UIKit?" beats "Tell me about SwiftUI".
- Add context. "Should we use a monorepo? Context: 8 microservices, 3 teams, Node+Go" produces sharper claims.
- 2–3 agents is the sweet spot. Agents in the same round are dispatched in parallel, so wall-clock is dominated by rounds rather than agent…
- Use --action when consensus should drive code changes or another real-world side-effect.
What it can do on your machine
Read from SKILL.md and the folder at commit 7939e67. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires argue CLI (@onevcat/argue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini, claude, etc.). API-based providers need API keys in environment.
From compatibility in the SKILL.md frontmatter.
Context cost
Argue loads about 1.9k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 580 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from onevcat/argue at commit 7939e67, republished under its MIT licence (© onevcat). 580 words, ~1,902 tokens.
Download SKILL.mdSave it as
.claude/skills/argue/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- argue
- description
- Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers. Use when facing strategic decisions, ambiguous trade-offs, architecture debates, or questions where multiple perspectives improve the answer. Triggers on: argue, debate, cross-examine, second opinion, multi-agent, 'Should we X or Y?' with real stakes, consensus-building, risk analysis, or confirmation-bias mitigation.
- compatibility
- Requires argue CLI (@onevcat/argue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini, claude, etc.). API-based providers need API keys in environment.
- license
- MIT
- metadata.author
- onevcat
- metadata.repo
- https://github.com/onevcat/argue
Argue — Multi-Agent Debate Engine
Structured debates where AI agents analyze independently, cross-examine across rounds, and converge on consensus through voting. Higher-confidence answers than any single model alone.
When to Use
✅ Strategic / architectural decisions with real trade-offs, "Should we X or Y?" with real stakes, risk analysis, confirmation-bias mitigation, pre-commit quality gates on big decisions.
❌ Simple factual lookups, time-critical tasks (debates take 3–7 minutes), open-ended creative generation, questions with obvious answers.
Pre-flight
If argue is not on PATH, install it (confirm with the user first — this is a global install):
npm install -g @onevcat/argue-cliThen verify and configure:
argue version # verify installed (v0.2+)
argue config init --global # ~/.config/argue/config.json — recommended for agent use
# Add at least 2 agents — `--agent <id>` shorthand creates provider + agent in one shot
argue config add-provider --id codex --type cli --cli-type codex --model-id gpt-5.4 --agent codex-agent
argue config add-provider --id gemini --type cli --cli-type gemini --model-id gemini-3.1-pro-preview --agent gemini-agentWhy global by default: a global config is set up once and works from any cwd, and outputs go to ~/.argue/output/<requestId>/ instead of cluttering the current project tree. Use argue config init --local only when a specific project needs its own dedicated agent line-up — that writes ./argue.config.json and outputs to ./out/<requestId>/.
For API providers, SDK adapters, roles, and system prompts, see references/setup.md.
Running Debates
# Basic — 2 agents, 2-3 rounds, auto-consensus
argue run --task "Should we use a monorepo or polyrepo?" --verbose
# With a follow-up action: representative executes once consensus is reached
argue run \
--task "Review the API design in docs/api.md" \
--action "Implement the consensus recommendation and open a PR" \
--verbose
# Open the rendered report in the hosted viewer when the run finishes
argue run --task "..." --viewUseful flags (full list: argue --help):
| Flag | Purpose |
|---|---|
--agents a,b | Pick which agents participate (default: defaults.defaultAgents from config, else all configured agents) |
--min-participants <n> | Minimum surviving participants required to continue (default: 2) |
--on-insufficient-participants interrupt|fail | When too few participants remain, either emit interrupted (default) or fail hard |
--min-rounds / --max-rounds | Control debate depth (defaults: 2 / 3) |
--threshold <0..1> | Consensus threshold (default: 1 = unanimous) |
--action <prompt> | Execute task after consensus |
--view / --viewer-url <url> | Open report in the hosted viewer |
--input <file> | JSON input for complex setups |
--verbose / -v | Stream agent reasoning live |
Debates typically take 3–7 minutes for 2 agents × 3 rounds. Default cap is 20 min per round (and per task, which tracks the round cap by default); bump --per-round-timeout-ms for heavy reviews.
Viewing & Acting on Results
When a run finishes, argue prints the request id and a viewer hint. Open it any time:
argue view # most recent run
argue view <request-id> # specific runThe hosted viewer renders result.json entirely client-side (gzip + base64url in the URL fragment — nothing is uploaded). Use --viewer-url to point at a self-hosted viewer.
To run a follow-up task using a debate result as context:
argue act --result ~/.argue/output/<requestId>/result.json --task "Write a summary blog post"
argue act --result ./out/<requestId>/result.json --task "Implement the changes" --agent codex-agentShow full SKILL.md (246 more words)Show less
Output Files
After every run, argue writes to ~/.argue/output/<requestId>/ (global config) or ./out/<requestId>/ (project-local config):
result.json— full structured resultsummary.md— markdown report (written on completion)events.jsonl— event stream (written live, survives crashes — parse it for partial results if a run is killed)error.json— error details (only on failure)
Result status: consensus | partial_consensus | unresolved | interrupted | failed.
If a debate drops below the required participant count, prefer the default interrupted path so downstream tools still get a structured result. Only force onInsufficientParticipants: "fail" when the caller explicitly needs legacy hard-failure semantics.
If you need to parse result.json programmatically, the canonical schema lives at packages/argue/src/contracts/result.ts.
Tips
- Frame as decisions, not topics. "Should we use SwiftUI or UIKit?" beats "Tell me about SwiftUI".
- Add context. "Should we use a monorepo? Context: 8 microservices, 3 teams, Node+Go" produces sharper claims.
- 2–3 agents is the sweet spot. Agents in the same round are dispatched in parallel, so wall-clock is dominated by rounds rather than agent count — adding more agents barely costs time. The real cost is tokens: every extra agent produces its own claims, plus every other agent has to read them as peer context, so token usage grows roughly with N². If the user's config has more than 3 agents, pass
--agents a,b,cexplicitly to pick a focused subset, or setdefaults.defaultAgentsin the config file once. - Use
--actionwhen consensus should drive code changes or another real-world side-effect.
Troubleshooting
For common errors and fixes, see references/troubleshooting.md.
© onevcat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/argue of onevcat/argue.
- SKILL.md
- references/setup.md
- references/troubleshooting.md
Open the folder on GitHubat commit 7939e67
Compare with similar skills
Argue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Argue this skillonevcat/argue | 279 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Orca CLIstablyai/orca | 87k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Mission Control Agent API
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
More from onevcat/argue
Release
onevcat/argue
Prepare and publish a new release — bump versions, generate changelog, tag, and push for CI to publish to npm.
Related
Categories
Questions about Argue
What does Argue do?
Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers. Argue is an agent skill from onevcat/argue. Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers.
When should I use Argue?
Argue fits situations like: facing strategic decisions; ambiguous trade-offs; architecture debates; questions where multiple perspectives improve the answer.
How do I install Argue in Claude Code?
Run `npx skills add onevcat/argue --skill argue -a claude-code`. Or copy the skill folder (skills/argue in onevcat/argue) into .claude/skills/argue in your project. Claude Code loads it when a task matches its description.
How do I install Argue in Codex?
Run `npx skills add onevcat/argue --skill argue -a codex`. Or copy the skill folder (skills/argue in onevcat/argue) into .agents/skills/argue in your project. Codex loads it when a task matches its description.
Can I use Argue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add onevcat/argue --skill argue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/argue, .gemini/skills/argue, .github/skills/argue and .opencode/skills/argue in your project.
What does Argue need to run?
Going by SKILL.md and its folder, Argue needs the command-line tools its instructions call (npm). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires argue CLI (@onevcat/argue-cli v0.2+) and at least 2 configured agents. CLI-based providers need their respective CLIs installed (codex, gemini, claude, etc.). API-based providers need API keys in environment..
Does Argue access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Argue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Argue use?
Argue is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Argue use?
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Argue?
Skills that share tags, products or a category with Argue: Orca CLI (stablyai/orca, 87k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Argue?
onevcat (a GitHub user) maintains it in onevcat/argue, which has 279 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 31, 2026.
Source: onevcat/argue on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.