Agent skill · software engineering · aiskillstore
computer-use
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".
Why this skill is useful
Adds executable commands for desktop app interaction that are not commonly known or documented.
What it needs
Requires orca installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Computer Use Use this skill for desktop UI through orca computer. When the requested target is a website or web app, operate the desktop browser app/window that contains the page. Preconditions Choose the Orca executable once: use the ORCACLICOMMAND environment value when set; otherwise use orca-dev in a dev session exposing ORCADEVREPOROOT, orca-ide on Linux outside an Orca-managed terminal, and orca everywhere else. Never try bare orca first on unmanaged Linux because it normally resolves to the GNOME screen reader. In every command example, ORCA is a documentation placeholder — including examples that name a specific shell. Replace it with that chosen executable before running the command; do not create a shell variable or run ORCA literally. Blocks that name no shell are intentionally shell-neutral for POSIX shells, PowerShell, and cmd.exe. Prefer --json. Screenshot bytes are omitted from JSON and written to screenshot.path. Do not push, submit forms, send messages, buy items, delete data, change account settings, or expose secrets unless the user explicitly asked for that action. If an app contains sensitive content, read only what the user requested. Core Loop Use the fresh state returned by each action for the next element index. Element indexes are the numeric labels shown in the tree; they may be sparse when noisy sections are omitted, so never infer valid indexes from elementCount or "Visible elements." Element indexes are short-lived and go stale after delays, navigation, focus changes, scrolling, window changes, or app re-rendering. In --json output, read the accessibility tree and action indexes from result.snapshot.treeText; elementCount is only a count and must not be used to infer indexes. App Selectors Prefer bundle IDs from list-apps; names are acceptable when unambiguous. Use pid:<number> only when bundle ID or name matching is ambiguous. For apps with multiple windows or ambiguous titles, run list-windows first. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/computer-use