Cua Driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
Install
npx skills add davidondrej/skills --skill cua-drivergit clone --depth 1 https://github.com/davidondrej/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/cua-driver ~/.claude/skills/cua-driverPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cua Driver
Cua Driver is an MIT-licensed local automation tool, not a model. Pi or another
agent supplies the reasoning; the driver reads accessibility trees/screenshots
and sends input to apps. No Cua cloud account or VM is needed. Host control is
not sandboxed, and desktop content sent to a cloud model leaves the machine.
## Before acting
```bash
command -v cua-driver
cua-driver --version
cua-driver status
cua-driver permissions status --json
```
Missing driver, stopped daemon, or missing Accessibility: stop and read
[setup](references/setup.md). Without Screen Recording, use accessibility-only
snapshots (`include_screenshot:false`); do not attempt screenshots or pixel input.
Never trigger permission prompts automatically. Respect any configured policy;
a skill does not grant permissions. Do not add restrictions or timeouts unless requested.
## Observe → act → verify
1. Prefer Bash/APIs for straightforward non-GUI work; use Cua when those routes are insufficient or the user requests GUI interaction. Use DeepAPI for web research.
2. Discover the intended app/window with `list_apps` / `list_windows`.
3. Read `cua-driver describe TOOL` before using unfamiliar parameters.
4. Get fresh `get_window_state` for the exact `pid` and `window_id`.
- Target an `element_token` (`<snapshot_id>:N`). Driver 0.34+ no longer accepts `element_index`.
- For pixels, read the same window's screenshot. Never guess coordinates or mix Retina points with screenshot pixels.Details
- Skill name
cua-driver- Repository
- davidondrej/skills
- Path
skills/cua-driver/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Cua Driver skill do?
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
How do I install the Cua Driver skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add davidondrej/skills --skill cua-driver. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cua Driver popular?
It lives in davidondrej/skills, which has 4,336 GitHub stars and 628 forks.
Related skills
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
4x4
4.3kdavidondrej/skills
Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.
Adr Verbatim
4.3kdavidondrej/skills
Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.
Root Cause Tracing
2.2kmrgoonie/claudekit-skills
Traces errors to find original triggers. Systematically trace through error chains to identify the root cause.
Workflow Threads Manager
7.7kMengTo/Skills
Oversee the other Claude threads (sessions) working on the same project. Check what each is doing, confirm finished work is merged to main, has its changelog entry with screenshots, and is live, archive threads that are truly done, and restart or flag threads that were cut off. Use when the user says "check threads", "check new changes", "are the threads merged and pushed", "archive the done threads", or asks what the other sessions are up to. Project specifics (changelog format, live site, capture folders) go in an optional local references/<project>.md next to this skill.
37signals Way
2.7kwondelai/skills
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, bet
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.