orchestration

Orca orchestration provides a structured coordination layer for multi-agent systems, enabling task dispatch, dependency tracking via DAGs, and lifecycle management through worker completion signals.

11.8K

Installs

Use cases

5/10

Quality

Is orchestration safe to install?

Review the source first

Review the source first: our audit of orchestration's source files found 24 shell commands, 0 external URLs, no file writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands via the Orca CLI to manage runtime state, dispatch tasks, and control terminal sessions.

How we audit skills: our security review methodology.

Who is this skill for?

Developers and AI agents using the Orca runtime to manage complex, multi-step workflows that require supervision, monitoring, or task-based coordination.

What can you do with it?

Dispatching structured tasks to worker agents and waiting for completion signals.
Managing task dependencies and DAGs.
Implementing coordinator loops and decision gates for multi-agent workflows.
Handling blocking ask/reply flows between agent terminals.

How good is this skill?

Quality score: 5/10. The documentation clearly distinguishes between supervised orchestration and full handoffs, providing specific command examples for both scenarios.

What does the skill file contain?

SKILL.md

# Orca Inter-Agent Orchestration

Orchestration is Orca's structured coordination layer for agent messages, task ownership, dispatch state, and worker completion tracking.

Use this skill when coordination state matters. For lightweight terminal prompts or basic worktree/terminal/built-in-browser control, use `orca-cli`.

## When To Use

- Send/reply/ask between agent terminals with persistent messages.
- Dispatch structured tasks to workers and wait for `worker_done` or `escalation`.
- Track task DAGs with dependencies.
- Run coordinator loops or decision gates.

Do not use orchestration mere...

Frequently asked questions

When should I use orchestration versus a simple handoff?

Use orchestration when you need to supervise, monitor, track completion, or coordinate a DAG. Use a simple handoff for full ownership transfers where the original agent does not need to wait for results.

How do I handle long-running tasks?

Use `orca orchestration check --wait` with a specified timeout. Treat timeouts as checkpoints rather than failures, as coding tasks often take 15-60 minutes.

What is the purpose of the --inject flag?

The `--inject` flag sends a task specification and a preamble into an agent CLI, enabling the agent to report lifecycle events like `worker_done` back to the coordinator.

Data sourced from stablyai/orca on GitHub. Install counts from skills.sh. The summary and security audit are derived from the skill's source files: every command and URL listed appears verbatim in the source.

Install

Works with Claude Code, Cursor, Codex CLI, and 50+ agents.

Manual install paths per agent

Claude Code: .claude/skills/ or ~/.claude/skills/

Codex CLI: .codex/skills/ or ~/.codex/skills/

GitHub Copilot: .github/skills/ or ~/.copilot/skills/

Amp: .agents/skills/ or ~/.config/agents/skills/

Copy the skill folder (with SKILL.md) into the project or global directory.

Security audit

high risk

Commands

URLs

File I/O

The skill executes shell commands via the Orca CLI to manage runtime state, dispatch tasks, and control terminal sessions.

View commands and endpoints

$ orca orchestration task-list --json

$ orca terminal list --json

$ orca orchestration dispatch-show --task <task_id> --json

$ orca orchestration send --to <handle|@group> --subject <text> [--from <handle>] [--body <text>] [--type <type>] [--priority <level>] [--thread-id <id>] [--payload <json>] [--json]

$ orca orchestration check [--terminal <handle>] [--unread] [--types <type,...>] [--inject] [--wait] [--timeout-ms <n>] [--json]

$ orca orchestration reply --id <msg_id> --body <text> [--from <handle>] [--json]

$ orca orchestration ask --to <handle> --question <text> [--options <csv>] [--timeout-ms <n>] [--from <handle>] [--json]

$ orca orchestration inbox [--limit <n>] [--json]

Sourcestablyai/orca

Installs11.8K

Quality5/10

orchestration multi-agent automation workflow

Related skills

find-skills

2.3M

Users seeking to extend agent capabilities with specialized tools, workflows, or knowledge packages

The find-skills skill enables agents to search for, discover, and install modular packages from the open agent skills ecosystem using the Skills CLI.

highclipackage-managervercel-labs

video-edit

338.7K

Users of the RunComfy CLI who need to automate video editing tasks like restyling, background swapping, or motion transfer

The video-edit skill acts as a router for the RunComfy CLI, selecting between Wan 2.7 Edit-Video, Kling 2.6 Pro Motion Control, and Lucy Edit Restyle models based on user intent to perform video transformations.

highvideo-editingai-agentagentspace-so

lark-doc

305.2K

Users who need to automate document management, content updates, and media handling within the Lark/Feishu ecosystem

The lark-doc skill enables agents to read, create, and edit Lark (Feishu) documents, including Docx and Wiki formats. It supports content manipulation via XML or Markdown, media handling, and resource management for document covers. The skill integrates with other Lark skills by identifying and delegating operations for embedded objects like spreadsheets, databases, and mind notes.

highLarkFeishularksuite

brainstorming

256.4K

Developers and project managers who need to define requirements, architecture, and design for software projects before writing code

A structured brainstorming framework that guides users through project exploration, design proposal, and specification before implementation. It enforces a strict design-first workflow, requiring user approval for designs and documentation before transitioning to the writing-plans skill.

mediumdesignplanningobra