What problem does it solve? Operating real Windows desktop applications programmatically is hard: windows may lack automation APIs, background input gets dropped, and clicks often fail silently. This Skill drives the local Windows desktop through the cua-driver MCP tools, letting you enumerate windows, read accessibility trees and screenshots, click, type, scroll, and verify that actions actually took effect. ## Core Features & Use Cases - Snapshot-bound element addressing: Capture a window's accessibility tree and screenshot with cua_get_window_state, then act on elements by index tied to that snapshot, avoiding stale-reference errors. - Background-first input delivery: Click, type, and set control values without stealing focus or moving the real mouse, with a structured escalation ladder to foreground mode only when required (e.g., Chromium keystrokes). - Action verification and pixel fallback: Re-read window state to confirm effects, and fall back to screenshot-based pixel coordinates for self-drawn UIs like WeChat that expose no accessibility tree. - Use Case: Ask the agent to open Calculator via its AUMID, read the window state, click buttons 4, +, 2, =, then re-read the result field to confirm it displays 6 — all without touching your real mouse. ## Quick Start Use the cua-driver skill to open Windows Calculator, compute 40 + 2, and verify the result shown on screen.