orchestration

bởi stablyai

We need to translate the given text from English to Vietnamese, preserving the name "orchestration" and technical terms like "orca-cli", "task DAGs", etc. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "orchestration" appears in the source text as "Orca orchestration" - so we should translate "orchestration" as part of the phrase? The instruction says "Preserve product names, protocol names, URLs, numbers, and technical terms." "Orca" is a product name, "orchestration" might be a technical term but it's also part of the product name? The instruction says "Name to preserve: orchestration" - that means we should keep the word "orchestration" as is, not translate it. But in the source text, it's "Orca orchestration" - so we keep "Orca orchestration" as is? The instruction says "Do not include the name unless it appears in the source text

npx skills add https://github.com/stablyai/orca --skill orchestration

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.

Thêm skills từ stablyai

computer-use
stablyai
We need to translate the given text from English to Vietnamese, preserving the name "computer-use" and other technical terms. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "computer-use" appears in the source text as "computer-use CLI" and also in the triggers list as "computer use" (without hyphen). We should preserve the exact form as in source: "computer-use" when it appears with hyphen, and "computer use" when without. Also preserve "Orca", "CLI", "UI", "Spotify", "Slack", etc. No extra commentary. Let's translate paragraph by paragraph. First sentence: "Use Orca's computer-use CLI to inspect and operate local desktop app windows through accessibility trees, screenshots, and safe UI actions." -> "Sử dụng CLI computer-use của Orca để kiểm tra và vận hành các cửa sổ ứng dụng desktop cục bộ thông qua cây trợ năng,
browser-automationtestingapi
orca-cli
stablyai
Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Orca browser", or "control the browser inside Orca"....
developmentbrowser-automationproductivity