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`).
Installs into .claude/skills of the current project.
Are you the author of Computer Use?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/michelkerkmeester-computer-use)
---
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 `skills get` is unknown, explain that updating Orca restores the guide; use
`--help` for read-only discovery and do not guess unsupported commands.