Agtx Task Sweep
fynnfluegge/agtx
Breaks a conversation's results into feature-level tasks and pushes them to the agtx kanban board, where each task gets its own worktree and agent session.
“Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and…”
$ npx skills add stablyai/orca --skill orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stablyai/orca orchestration --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/stablyai/orca.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchestration .claude/skills/orchestration && 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 "orchestration" agent skill from https://github.com/stablyai/orca/tree/main/skills/orchestration into .claude/skills/orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestration", 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/stablyai/orca/tree/main/skills/orchestrationType 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 stablyai/orca --skill orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stablyai/orca orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stablyai/orca.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/orchestration .agents/skills/orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestration" agent skill from https://github.com/stablyai/orca/tree/main/skills/orchestration into .agents/skills/orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestration", 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 stablyai/orca --skill orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stablyai/orca orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stablyai/orca.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/orchestration .cursor/skills/orchestration && 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 "orchestration" agent skill from https://github.com/stablyai/orca/tree/main/skills/orchestration into .cursor/skills/orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestration", 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/stablyai/orca.git --path skills/orchestration--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 stablyai/orca --skill orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stablyai/orca orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stablyai/orca.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/orchestration .gemini/skills/orchestration && 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 "orchestration" agent skill from https://github.com/stablyai/orca/tree/main/skills/orchestration into .gemini/skills/orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestration", 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 stablyai/orca orchestrationInstalls 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 stablyai/orca --skill orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stablyai/orca.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/orchestration .github/skills/orchestration && 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 "orchestration" agent skill from https://github.com/stablyai/orca/tree/main/skills/orchestration into .github/skills/orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestration", 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 stablyai/orca --skill orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stablyai/orca orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stablyai/orca.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/orchestration .opencode/skills/orchestration && 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 "orchestration" agent skill from https://github.com/stablyai/orca/tree/main/skills/orchestration into .opencode/skills/orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestration", 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.
orchestration“Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and decomposing work across agents. Use `orca-cli` for full ownership handoffs — "hand off", "handoff", "handover", "give this to another agent", "another worktree" — unless asked to supervise, monitor, or coordinate a DAG, and for terminal control, lightweight terminal prompts, shell commands, Orca worktree management, and reading or waiting on terminals.”
Orca Orchestration is a skill in stablyai/orca (87k stars). Its SKILL.md is about 916 tokens. Licence: MIT.
Read from SKILL.md and the folder at commit 61de2d8. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Orca Orchestration loads about 916 tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 445 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.
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.
The full file from stablyai/orca at commit 61de2d8, republished under its MIT licence (© stablyai). 445 words, ~916 tokens.
.claude/skills/orchestration/SKILL.md (or your agent's skills folder).This file is a discovery stub, not the usage guide. The full, version-matched Orca
orchestration reference is served by the orca binary itself — kept out of this file on
purpose so it can never drift from the binary that will actually run your commands.
Engage Orca orchestration whenever you need structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill instead for full ownership handoffs ("hand off", "handoff", "handover", "give this to another agent", "another worktree") when the user did not ask to supervise, monitor, wait for results, or coordinate a DAG — and for ordinary terminal control, shell commands, worktree management, and the built-in browser. Coordination requires real Orca runtime state; never substitute a non-Orca subagent tool.
Choose the executable once and reuse it for every later command:
ORCA_CLI_COMMAND environment variable is set, use its value. Orca exports this
for managed WSL sessions.ORCA_DEV_REPO_ROOT, use orca-dev.orca-ide. Never run bare
orca there — outside Orca's terminals it normally resolves to the
GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine.orca.Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run ORCA literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.
ORCA skills get orchestrationThat prints the compact, version-matched guide for the exact binary that will handle your
next commands. It covers the normal local coordinator loop. For a conditional action gate
such as remote placement, uncertain release recovery, or expanded DAG work, load only the
reference that gate names with
ORCA skills get orchestration --reference references/<file>.md
(--references lists the names). If that binary rejects --reference, run
ORCA skills get orchestration --full and read the named bundled reference before acting.
Prefer --json. Use the selected executable's --help for commands or flags the guide does
not cover. If a command reports that Orca is not running, start it with ORCA open --json
and retry. If it fails with runtime_access_denied, your sandbox blocked the connection:
re-run it with escalated permissions, and do not run ORCA open or restart Orca. If
skills get is unknown, explain that updating Orca restores the guide; use --help for
read-only discovery and do not guess unsupported commands.
© stablyai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/orchestration of stablyai/orca.
Open the folder on GitHubat commit 61de2d8
Orca Orchestration 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 |
|---|---|---|---|---|---|---|
| Orca Orchestration this skillstablyai/orca | 87k | — | ~916 | Automated safety check: Pass | MIT | |
| Agtx Task Sweepfynnfluegge/agtx | 1.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| GSD Quick Batchopen-gsd/gsd-core | 10k | — | ~1.4k | Automated safety check: Notes | MIT | |
| ClawTeam Multi-Agent Swarmwin4r/ClawTeam-OpenClaw | 1.5k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| MemPalace Task HandoffMemPalace/mempalace | 59k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Agent of Empires Session Manageragent-of-empires/agent-of-empires | 3.3k | — | ~2.5k | Automated safety check: Pass | MIT |
fynnfluegge/agtx
Breaks a conversation's results into feature-level tasks and pushes them to the agtx kanban board, where each task gets its own worktree and agent session.
open-gsd/gsd-core
Runs several small /gsd-quick tasks as one batch, with a single coordinator that plans them, dispatches workers per item and owns all shared writes and worktree merges.
win4r/ClawTeam-OpenClaw
Launches a swarm of specialist Hermes agents in git-worktree-isolated tmux windows with a kanban board and file-based inboxes, using built-in templates like hedge-fund and code-review.
MemPalace/mempalace
Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.
agent-of-empires/agent-of-empires
Launches, monitors and organizes AI coding agent sessions such as Claude Code or Codex inside tmux, tracking status, capturing output and managing git worktrees for parallel branches.
alchaincyf/huashu-skills
多Agent蜂群并行协作,纯git自组织,适合大型项目开发。当用户提到"蜂群模式"、"多agent"、"并行开发"、"agent swarm"时使用。
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
stablyai/orca
iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…
stablyai/orca
Linear ticket work through Orca's CLI. Use when working from a linked Linear issue, finishing work with a PR/MR link and a completion comment, moving a ticket…
stablyai/orca
Set up, review, debug, or validate an Orca per-workspace environment recipe: the on-demand, disposable runtime (cloud sandbox, VM, SSH host, or local…
stablyai/orca
Drives the GUI of a visible local app window through `orca computer`: accessibility tree, clicks, typing, menus, dialogs, and screenshots in native apps and…
stablyai/orca
Linear ticket work through Orca's CLI. Use when working from a linked Linear issue, finishing work with a PR/MR link and a completion comment, moving a ticket…
Categories
Run `npx skills add stablyai/orca --skill orchestration -a claude-code`. Or copy the skill folder (skills/orchestration in stablyai/orca) into .claude/skills/orchestration in your project. Claude Code loads it when a task matches its description.
Run `npx skills add stablyai/orca --skill orchestration -a codex`. Or copy the skill folder (skills/orchestration in stablyai/orca) into .agents/skills/orchestration in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stablyai/orca --skill orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestration, .gemini/skills/orchestration, .github/skills/orchestration and .opencode/skills/orchestration in your project.
SKILL.md names no scripts, command-line tools or credentials: Orca Orchestration is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Orca Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 916 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Orca Orchestration: Agtx Task Sweep (fynnfluegge/agtx, 1.7k stars), GSD Quick Batch (open-gsd/gsd-core, 10k stars), ClawTeam Multi-Agent Swarm (win4r/ClawTeam-OpenClaw, 1.5k stars) and MemPalace Task Handoff (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
stablyai (a GitHub organization) maintains it in stablyai/orca, which has 87,277 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.
Source: stablyai/orca on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.