bystablyai· 16 skills
Use Orca's computer-use CLI to inspect and operate local desktop app windows through accessibility trees, screenshots, and safe UI actions. Use for desktop app interaction: list apps/windows, get app state, read visible UI, click controls, type, press keys, scroll, drag, set values, or perform accessibility actions. Also use for browser windows, webviews, Orca app UI, or other desktop UI. Triggers include "computer use", "orca computer", "read Spotify", "read Slack", "control/click/read in a desktop app", and "get app state".
$npx -y skills add stablyai/orca --skill computer-useInstalls into the current project.
Run `npx skills use "https://github.com/stablyai/orca" --skill "stablyai/orca/computer-use"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/stablyai/orca" that are relevant to the current task. Run `npx skills add "https://github.com/stablyai/orca"` and select the relevant skills, then follow their instructions.
| 1 | # Computer Use |
| 2 | |
| 3 | This file is a discovery stub, not the usage guide. The full, version-matched computer-use |
| 4 | reference is served by the `orca` binary itself — kept out of this file on purpose so it can |
| 5 | never drift from the binary that will actually run your commands. |
| 6 | |
| 7 | Engage Orca's computer-use surface whenever you must inspect or operate a local desktop app |
| 8 | window — reading its accessibility tree, taking screenshots, or performing safe UI actions |
| 9 | (click controls, type, press keys, scroll, drag, set values). It also covers browser |
| 10 | windows, webviews, and Orca's own UI. Triggers include "computer use", "orca computer", |
| 11 | "read Spotify", "read Slack", "control/click/read in a desktop app", and "get app state". |
| 12 | |
| 13 | ## Resolve the CLI for this session |
| 14 | |
| 15 | Choose the executable once and reuse it for every later command: |
| 16 | |
| 17 | - If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this |
| 18 | for managed WSL sessions. |
| 19 | - Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`. |
| 20 | - Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare |
| 21 | `orca` there — outside Orca's terminals it normally resolves to the |
| 22 | GNOME Orca screen reader (`/usr/bin/orca`) and starts speech on the user's machine. |
| 23 | - Otherwise, use `orca`. |
| 24 | |
| 25 | Below, `ORCA` is a placeholder for the executable you resolved. Substitute it before |
| 26 | running anything; do not create a shell variable or run `ORCA` literally. This works the |
| 27 | same way in POSIX shells, PowerShell, and cmd.exe. |
| 28 | |
| 29 | If the selected executable cannot run, report its exact error and stop. Do not fall through |
| 30 | to another executable, which could silently target a different Orca build. |
| 31 | |
| 32 | ## Load the full guide before running Orca commands |
| 33 | |
| 34 | ```text |
| 35 | ORCA skills get computer-use |
| 36 | ``` |
| 37 | |
| 38 | That prints the complete, version-matched guide for the exact binary that will handle your |
| 39 | next commands — listing apps/windows, reading UI, and driving clicks, typing, and other |
| 40 | accessibility actions. Read it first, then run the specific command you need. |
| 41 | |
| 42 | Don't guess subcommands or flags from memory or from a cached copy of this stub. They |
| 43 | change between Orca releases, and this file deliberately no longer lists them. Confirm the |
| 44 | app is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and |
| 45 | prefer `--json` for agent-driven calls. |
| 46 | |
| 47 | ## If an older Orca does not recognize `skills get` |
| 48 | |
| 49 | Use this fallback only when the selected binary explicitly reports that `skills get` is an |
| 50 | unknown command. Another failure is not proof of an older binary; report it rather than |
| 51 | guessing or changing executables. For a confirmed pre-guide binary, use only this bounded, |
| 52 | read-only bootstrap to orient. Do not dead-end and do not invent commands: |
| 53 | |
| 54 | ```text |
| 55 | ORCA status --json |
| 56 | ORCA computer capabilities --json |
| 57 | ORCA computer list-apps --json |
| 58 | ``` |
| 59 | |
| 60 | Then tell the user that updating Orca restores the full, version-matched guide via |
| 61 | `ORCA skills get computer-use`. Beyond these commands, ask the user rather than guessing a |
| 62 | command surface this older binary may not support. |