Add a DeepChat LLM provider through explicit reviewed source changes. Use when a developer asks Codex to add a provider, provider profile, upstream provider config, model catalog mapping, provider auth behavior, or a special provider adapter in this repository.
cua-driver
cua-driver is an open-source integrations skill for Claude Code and compatible agents, published by ThinkInAIXYZ. Its author describes it as: “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. Use when the user asks you to operate, drive, automate, or perform a GU…”. The project has 6.2k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/cua-driver`.
What cua-driver does
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.
Installation
Add cua-driver to your agent with:
git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/cua-driver Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for cua-driver is organised into these sections:
- DeepChat MCP mode
- Sparse visible UI fallback
- The no-foreground contract — read this first
- Defaults — always prefer cua-driver over shell shims
- The narrow carve-out
- Self-check pattern
- Prerequisites — check before starting
- Using cua-driver from the shell
- Agent cursor overlay
- The core invariant — snapshot before AND after every action
- Why window selection is the caller's job now
- Behavior matrix
When to use it
Reach for cua-driver when you want integrations help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear Apache-2.0 license — safe to read and adapt
- Ships in ThinkInAIXYZ/deepchat, an established project with 6,228 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does cua-driver do?
- 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. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers").
- How do I install cua-driver?
- Run git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/cua-driver in your agent, then reload your skills. Review the source at https://github.com/ThinkInAIXYZ/deepchat before installing.
- Is cua-driver free to use?
- Yes. cua-driver is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
- Where does cua-driver come from?
- cua-driver ships inside ThinkInAIXYZ/deepchat, a repository that contains 25 catalogued skills in total. The repository's 6,228 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Integrations →Drive native desktop apps through DeepChat's built-in Computer Use tools. Use when the user asks to operate, inspect, automate, or perform a GUI task in a real desktop application.
Use the Feishu/Lark plugin MCP tools for Feishu documents, spreadsheets, knowledge content, and other matching workspace operations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
DeepChat app settings modification (DeepChat 设置/偏好) skill. Activate ONLY when the user explicitly asks to change DeepChat's own settings/preferences (e.g., theme, language, font size...). Do NOT activate for OS/system settings, editor settings, or other apps.