Cua Driver
Drive a native GUI app (macOS, Windows, Linux) via the Qwen Cua Driver CLI (default) or...
Install
npx skills add QwenLM/qwen-code --skill cua-driver -g -a claude-code -y- Repository
- QwenLM/qwen-code28.9k
- Category
- Design
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Drive a native GUI app (macOS, Windows, Linux) via the Qwen Cua Driver CLI (default) or MCP server; snapshot its accessibility tree, act through snapshot-bound element tokens, native menu paths, exact window geometry, or pixel coordinates, and verify from fresh state. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real application on the host.
Qwen Cua Driver
Orchestrates cross-platform app automation via qwen-cua-driver. Whenever
a user asks to drive a native app, follow the loop in this skill
rather than calling tools ad-hoc, the snapshot-before-action
invariant is not optional and silently breaks if you skip it.
Platform-specific reading, read this first
This file is the cross-platform core: snapshot invariant, CLI vs MCP choice, tool surface naming, behavior matrix, canonical loop, pixel-click contract, common failure modes. The platform-specific material (forbidden-list, accessibility tree implementation, launch semantics, click dispatch) lives in companion files in this same directory:
- macOS, read
MACOS.md(no-foreground contract, forbiddenopen/osascript/cliclickinvocations, AXMenuBar navigation, SkyLight pixel-click dispatch). - Windows, read
WINDOWS.md(UIA tree vs AX, UWP / ApplicationFrameHost hosting, layered UIA+PostMessage click chain, Session 0 isolation, Windows-specific focus-steal vectors). - Linux, read
LINUX.md(X11 background input via AT-SPI + XSendEvent (including X11 apps under XWayland)).
Cross-cutting topics also have their own files:
BROWSER.md, exact native-window binding, explicit browser preparation, typed Chromium/Electron page tools, input trust classes, and native fallbacks for browser chrome and unsupported engines.RECORDING.md, session recording +replay_trajectory.
Use whichever combination matches the host. When in doubt, run
qwen-cua-driver doctor, it reports the platform and the right entry
point.
Start with the narrowest semantic route
Before opening or operating an application, name the desired postcondition and use the first applicable route below. Verify the result in the same domain before stopping or advancing:
