菜单
Use this skill when the user asks for Ghostex Computer Use, Desktop Control, or native macOS app automation. It wraps the Cua Driver workflow so agents can drive desktop apps without the user needing to remember `$cua-driver`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to execute a multi-phase coding task with a Fable-planned, Codex-implemented, Fable-verified pipeline inside Ghostex: the invoking session plans inline and writes a phase plan file, launches one Codex (gpt-5.5) worker pane per phase through the Ghostex CLI, then launches a Fable verifier pane that checks every acceptance criterion, and spawns targeted Codex fixer panes for any findings until verification passes or the fix loop cap is reached.
Use this skill when coordinating work across Ghostex panes or agent sessions through the Ghostex CLI: creating terminal or agent panes, listing sessions, checking agent status, sending messages to other agent sessions, reading the last lines from another session, focusing/sleeping/waking/killing sessions, or using Ghostex commands instead of raw zmx/tmux control.
Generate a concise Ghostex session title for the current thread or conversation. Use when the user asks for a thread name, chat title, session title, resume title, or any concise label summarizing what was worked on; then submit the rename command in the current Ghostex session.
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
Explain how to fork an existing Codex CLI session into another folder by using `/status` to get the session id and `codex fork --yolo -C TARGET_FOLDER SESSION_ID`. Use when a user asks to move the current Codex session, change the Codex working directory, fork a Codex conversation into a different project folder, or continue a Codex thread under another workspace root as a separate session.
Use this skill when adding, configuring, or troubleshooting agent access to Ghostex embedded CEF browser panes through the Ghostex Browser Use MCP workflow. It covers CLI installation, MCP config, page selection, console logs, DOM snapshots, clicks, fills, key presses, screenshots, and the CEF remote debugging port used by `ghostex browser mcp`.
| name | ghostex-computer-use |
| description | Use this skill when the user asks for Ghostex Computer Use, Desktop Control, or native macOS app automation. It wraps the Cua Driver workflow so agents can drive desktop apps without the user needing to remember `$cua-driver`. |
Use this skill when a task needs native macOS app automation through Ghostex
Desktop Control. This skill is intentionally a wrapper around $cua-driver: if
the $cua-driver skill is available, load it and follow its workflow exactly.
Use $ghostex-browser-use instead for Ghostex embedded browser panes.
Integrations.
cua-driver.Check the machine state before acting:
which cua-driver
cua-driver status
cua-driver check_permissions '{"prompt":false}'
If the daemon is not running, start it with:
open -n -g -a CuaDriver --args serve
cua-driver <tool> '<JSON>'.cua-driver mcp server for ordinary
Ghostex Computer Use. The CLI proxies through the signed CuaDriver.app daemon,
while global MCP registration can leave many stdio helper processes around.open -a, AppleScript activation, HID event injection, cliclick,
or menu-bar automation for background control.element_index values.Launch or find the app with Cua Driver, for example:
cua-driver launch_app '{"bundle_id":"com.apple.TextEdit"}'
Get the window state:
cua-driver get_window_state '{"pid":1234,"window_id":5678}'
Choose the target by element_index from the snapshot.
Perform one action such as click, type, scroll, drag, key press, or set value.
Re-run get_window_state and verify the expected UI state before continuing.
$cua-driver; this wrapper exists so users
can ask for $ghostex-computer-use.