computer-use
Computer Use
Use this skill when the task should operate through Orca's desktop computer-use surface rather than native Codex computer tools, raw AppleScript, ad hoc screenshots, or direct app internals.
Preconditions
- Prefer the public
orca computer ...command. - In this Orca worktree, use
./config/scripts/orca-dev computer ...when testing the local dev runtime. - Prefer
--jsonfor agent-driven calls. Screenshot image bytes are omitted from JSON and written toscreenshot.pathwhen present. - Do not push, submit forms, send messages, buy items, delete data, or change account settings unless the user explicitly asked for that specific action.
- If an app contains sensitive content, read only what the user requested and avoid unnecessary screenshots or logs.
Check runtime availability first:
orca status --json
orca computer capabilities --json
More from stablyai/orca
orca-cli
>-
877orchestration
>-
195electron
Launch, automate, and validate Electron desktop apps using playwright-cli via Chrome DevTools Protocol. Use this skill to validate UI changes in Orca, test features in the running Electron app, verify code fixes work end-to-end, or automate any Electron app (VS Code, Slack, Discord, etc.). Triggers include "validate in Electron", "test in the app", "verify the fix", "check the UI", "/electron", "automate Slack app", "control VS Code", or any task requiring interaction with a running Electron application.
4auto-pr-merge
Create PR, wait for checks, fix issues iteratively, and merge with --admin
4auto-review-fix
Automated iterative code review and fix loop with parallel review agents
4auto-submit
End-to-end autonomous pipeline that runs auto-review-fix, then auto-pr-merge
4