Orca computer use: GUI control via accessibility tree
Drive a visible app window through Orca's computer-use skill — clicks, typing, menus, dialogs and screenshots — only when code-based paths cannot work
- What
- Drive a visible app window through Orca's computer-use skill — clicks, typing, menus, dialogs and screenshots — only when code-based paths cannot work
- Cost
- Free
- Needs
- Orca installed (the executable matching this guide); nothing else required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @stablyai's discovery stub for Orca's computer-use capability: it teaches the agent to resolve the right Orca executable for the session (environment variables like ORCA_CLI_COMMAND, dev checkouts, `orca-ide` on Linux to avoid clashing with the GNOME Orca screen reader), then load the version-matched guide with `skills get computer-use` before driving a visible app window — accessibility tree, clicks, typing, menus, dialogs and screenshots across native apps, external browser windows (Chrome, Edge, Safari) and webviews. By @stablyai, listed here with credit to its creator. Honest caveats: the skill is a resolver stub — the full guide ships inside the Orca executable and is version-matched at runtime; it explicitly prefers programmatic paths (shell, filesystem, git, HTTP, existing CLIs) and treats GUI control as the last resort for windows those cannot reach; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Orca computer use is a free Muse skill and discovery stub for Orca's computer-use capability, driving a visible app window only when code-based paths cannot work. It teaches the agent to resolve the right Orca executable for the session, then load the version-matched guide with skills get computer-use, before clicks, typing, menus, dialogs and screenshots through the accessibility tree.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it📌 Pinned version: commit c9c6a00Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Orca installed (the executable matching this guide); nothing else required Install "Orca computer use: GUI control via accessibility tree" for me. It teaches the agent to resolve the correct Orca executable for the session and load the version-matched guide before driving a visible app window — accessibility tree, clicks, typing, menus, dialogs and screenshots — preferring programmatic paths (shell, filesystem, git, HTTP, existing CLIs) whenever they can complete the task. Repository: https://raw.githubusercontent.com/stablyai/orca/c9c6a00449eb72c41234940aead9832b8c46d030/skills/computer-use/SKILL.md Pinned version: install the code at commit c9c6a00449eb72c41234940aead9832b8c46d030 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "computer-use". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the Orca executable if missing, following the repo's own instructions; note that outside Orca's terminals, bare `orca` usually resolves to the GNOME Orca screen reader, not this tool). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c9c6a00 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox and failed · Nov 18, 2026 — Needs pnpm, npm cannot install it · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 3, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.