Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thinkinaixyz/cua-driver
Drive a native macOS app via the cua-driver MCP server or CLI — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot.
Passed 16 of 18 test cases with the skill, and 4 of 18 without it.
and 18 more in the full report
14 fixed5 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Specify the exact shell command to launch the background automation daemon for persistent element_index caching across CLI tool calls.
| Checked | Without skill | With skill |
|---|---|---|
| Uses open -n -g -a with the daemon bundle name and --args serve. | Missed | Passed |
The instructions your model reads when the skill loads.
Orchestrates macOS app automation via cua-driver. Whenever a user
asks to drive a native macOS 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.
When DeepChat auto-pins this skill because the Computer Use MCP server is
enabled, use the available Computer Use tools in the current tool list
directly. Treat examples such as click({...}) or
get_window_state({...}) as calls to the matching MCP tool with the same
JSON payload. Shell CLI examples are diagnostic references for
shell-based agents.
App-name resolution belongs here. When matching a user request to an
app, compare the request with each list_apps name and bundle_id.
Consider the user's language, system language, English product names,
English brand names, romanized or pinyin variants, and common
abbreviations. Treat bundle_id as the strongest identity signal. When
the requested app name is ambiguous, localized, translated, abbreviated,
or written in another script, call list_apps, resolve the most credible
bundle id, then call launch_app with that bundle id.
Many media and Electron apps expose a shallow AX tree while still
showing enough pixels to act. Spotify-style snapshots with only
AXWindow, title-bar buttons, and a menu bar are still actionable when
the screenshot shows a visible, unambiguous target.
For a user-requested non-destructive action, continue within the same turn through the safest visible options:
zoom on the relevant screenshot region when the screenshot is
wide, dense, or the target is small.test cases passed, vs 4 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.