SKILL DETAIL
computer-use
stablyai/orca/computer-use
This skill enables you to use Orca's computer-use CLI to inspect and operate local desktop app windows. It supports reading accessibility trees, taking screenshots, and performing safe UI actions such as clicking controls, typing, pressing keys, scrolling, dragging, and setting values. It applies to desktop apps, browser windows, webviews, and Orca's own UI. To use this skill, first resolve the appropriate CLI executable for your session (via the ORCA_CLI_COMMAND environment variable, orca-dev in a dev checkout, orca-ide on Linux outside Orca-managed terminals, or orca by default), then run `ORCA skills get computer-use` to load the full version-matched guide. The guide provides detailed commands and usage. If an older Orca does not recognize `skills get`, you can use a limited read-only bootstrap with commands like `ORCA status --json`, `ORCA computer capabilities --json`, and `ORCA computer list-apps --json` to orient, and inform the user that updating Orca restores the full guide.
Installation
npx skills add https://stablyai/orca/
스킬 파일
SKILL.md
최근 동기화 · 2026. 10. 22.
SKILL.md›
---
name: computer-use
description: >-
Drives the GUI of a visible local app window through `orca computer`: accessibility
tree, clicks, typing, menus, dialogs, and screenshots in native apps and external
browser windows (Chrome, Edge, Safari) or webviews. Prefer a programmatic path
(shell, filesystem, git, HTTP, existing CLIs) whenever it can complete the task.
Use only when a visible window needs GUI control those cannot reach. Do not use
for Orca's embedded browser (`orca-cli`).
---
# Computer Use
This discovery stub loads the version-matched guide from the Orca executable used for this session.
## 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
```text
ORCA skills get computer-use
```
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.