computer-use
/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".
- Author
- HK-hub ↗
- Repository
- AgentSkills ↗
- Licence
- MIT
- Last repository change
- 18.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author description
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".
How it works
- Resolve the CLI for this session
- Load the full guide before running Orca commands
- If an older Orca does not recognize skills get
SKILL.md preview
--- name: computer-use description: >- 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". --- # Computer Use This file is a discovery stub, not the usage guide. The full, version-matched computer-use reference is served by the `orca` binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands. Engage Orca's computer-use surface whenever you must inspect or operate a local desktop app window — reading its accessibility tree, taking screenshots, or performing safe UI actions (click controls, type, press keys, scroll, drag, set values). It also covers browser windows, webviews, and Orca's own UI. Triggers include "computer use", "orca computer", "read Spotify", "read Slack", "control/click/read in a desktop app", and "get app state". ## 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 full guide before running Orca commands ```text ORCA skills get computer-use ``` That prints the complete, version-matched guide for the exact binary that will handle your next commands — listing apps/windows, reading UI, and driving clicks, typing, and other accessibility actions. Read it first, then run the specific command you need. Don't guess subcommands or flags from memory or from a cached copy of this stub. They change between Orca releases, and this file deliberately no longer lists them. Confirm the app is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and prefer `--json` for agent-driven calls. ## If an older Orca does not recognize `skills get` Use this fallback only when the selected binary explicitly reports that `skills get` is an unknown command. Another failure is not proof of an older binary; report it rather than guessing or changing executables. For a confirmed pre-guide binary, use only this bounded, read-only bootstrap to orient. Do not dead-end and do not invent commands: ```text ORCA status --json ORCA computer capabilities --json ORCA computer list-apps --json ``` Then tell the user that updating Orca restores the full, version-matched guide via `ORCA skills get computer-use`. Beyond these commands, ask the user rather than guessing a command surface this older binary may not support.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HK-hub/AgentSkills | 100 | MIT |
| kirodotdev/kirocrew | 100 | Apache-2.0 |
| thesyart/emperor-agent | 100 | MIT |
| xuzhougeng/wisp-science | 100 | AGPL-3.0 |
| stablyai/orca | 100 | MIT |
| nexus-research-lab/nexus | 100 | Apache-2.0 |
| timharris707/skills | 100 | MIT |
| latestaiagents/agent-skills | 100 | MIT |
| bernardofernandezz/helix | 100 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version cda997a95fa7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100agent-desktop
Operate desktop applications on macOS, Windows and Linux through native accessibility trees, using the agent-desktop CLI. Use when an AI agent must see or act on a desktop GUI: click buttons, fill forms, read UI state, navigate menus, toggle checkboxes, scroll, drag, type text,… - 95agent-desktop
Operate desktop applications on macOS, Windows and Linux through native accessibility trees, using the agent-desktop CLI. Use when an AI agent must see or act on a desktop GUI: click buttons, fill forms, read UI state, navigate menus, toggle checkboxes, scroll, drag, type text,… - 100agent-desktop
Operate desktop applications on macOS, Windows and Linux through native accessibility trees, using the agent-desktop CLI. Use when an AI agent must see or act on a desktop GUI: click buttons, fill forms, read UI state, navigate menus, toggle checkboxes, scroll, drag, type text,… - 100host-computer-use
Beta desktop control through the connected A0 CLI host. Use for the user's host/local computer screenshots, screen inspection, menus, native app UI, OS-level clicking, scrolling, typing, or checking computer_use_remote status. Use instead of linux-desktop for host/local machine… - 100agent-desktop
通过原生无障碍树,使用 agent-desktop CLI 在 macOS、Windows 和 Linux 上操作桌面应用。 适用于 AI agent 需要查看或操作桌面 GUI 的场景:点击按钮、填写表单、读取 UI 状态、导航菜单、 切换复选框、滚动、拖拽、输入文本、按下快捷键、截图、管理窗口、使用剪贴板、启动或关闭应用、 读取通知。 触发词:"click button"、"fill form"、"open app"、"read UI"、"computer use"、 "operate desktop"、"accessibility… - 100codex-computer-use
Control local apps through Computer Use (the @oai/sky runtime) inside the Codex app. Use when the session uses a custom (non-OpenAI) model, for example deepseek-v4-flash or mimo-v2.5, and the user asks to control the computer, operate a desktop app's UI, use Safari or Chrome…