Index of every page on this site: llms.txt
All skills
stablyai avatar
by Stablystablyai/orca130k stars
8,280
Run it yourself

Run work in separate Orca worker agents and get their results back. Use when the user invokes /orchestration, asks for Orca workers or supervision (monitor, task DAGs, ask/reply, decision gates), or asks to split, parallelize or fan out code changes across agents, worktrees or branches; use Orca workers for those. Also use when the work needs a different agent (such as Codex from Claude) or its own Orca workspace: "Have Codex (or Claude) review this and report back" means an Orca worker of that agent. Also use when you are a dispatched worker (a prompt with Task and Dispatch IDs: ask, worker_done). Unless the user asks for Orca workers or a named agent, searches, reads and research in your workspace stay with your own subagents, even in parallel. Use `orca-cli` to hand work off with nothing expected back ("hand off", "handover", "give this to another agent", "another worktree"), and for terminal control, shell commands, worktree management, and reading or waiting on terminals.

Use this Skill: https://skilld.dev/gh/stablyai/orca/orchestration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈252 tokens for metadata: the name and description. ≈716 when used: this file.

Description uses 12.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈1007 characters, or 12.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Orca Orchestration

This discovery stub loads the version-matched guide from the Orca executable used for this session.

Never substitute a non-Orca subagent tool when the user asked for Orca orchestration.

Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

  • If the ORCA_CLI_COMMAND environment variable is set, use its value. Orca exports this for managed WSL sessions.
  • Otherwise, in a dev checkout whose session exposes ORCA_DEV_REPO_ROOT, use orca-dev.
  • Otherwise, on Linux outside an Orca-managed terminal, use 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.
  • Otherwise, use 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.

Load the version-matched guide before running Orca commands

ORCA skills get orchestration

That prints the compact, version-matched guide for the exact binary that will handle your next commands. It covers the normal local coordinator loop and dispatched-worker obligations. 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.

Use the selected executable's --help for commands or flags the guide does not cover. A runtime_unavailable error is usually transient while Orca is busy or restarting: wait a few seconds and retry the command. Before retrying a command that changes something, check whether it already took effect, and reuse any request ID the error names. ORCA open can bring Orca's window to the front over the user's work, so never run it to retry a failed command. Run it only when the user asks, or when Orca is really not running: ORCA status --json reports result.app.running: false, or every command, ORCA status included, still cannot connect after about 30 seconds of retries. If a command 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alerttoday3 checks · Risk MEDIUM
  • Gen Agent Trust Hub1d

    This skill orchestrates tasks by executing local CLI tools and dynamically loading its own operating instructions from their output. It includes instructions to attempt execution with escalated system privileges if access is denied.

  • Sockettoday

    No alerts

  • Snyk1d

    Risk: CRITICAL · 2 issues

Signed by skilld at f2d58c9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for stablyai/orca/orchestration