Cmux
Control the cmux macOS terminal app: workspaces, panes, surfaces, browsers, notifications, settings, and hooks. Use only when the user explicitly names cmux. Read before running any cmux command.
Install
npx skills add davidondrej/skills --skill cmuxgit clone --depth 1 https://github.com/davidondrej/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/cmux ~/.claude/skills/cmuxPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# cmux Control macOS 14.0+. Prefer the CLI; if `cmux` is not on PATH, use `/Applications/cmux.app/Contents/Resources/bin/cmux`. ## Targeting and safety **Window → workspace → pane → surface:** macOS window → sidebar project/branch tab → split region → terminal, browser, or Markdown tab. - **Anchor to the caller's `CMUX_WORKSPACE_ID`.** Never assume the visually focused workspace is the target. Outside cmux, identify the intended workspace before acting. - **Use prefixed refs or UUIDs.** `workspace:2`, `pane:1`, `surface:7`; bare numbers are indexes, not IDs. Output defaults to refs; `--id-format uuids|both` includes UUIDs. - **Refresh targets.** Surface refs are global, not workspace-local. Re-list before reusing them; check `cmux surface-health` before sending input when state may be stale. - **Preserve focus.** Pass `--focus false` wherever supported. Use `select-workspace`, `focus-pane`, `focus-panel`, or `focus-surface` only on explicit user request. - **Respect ownership.** Never send input to surfaces you do not own. Stay in the caller's workspace unless the user explicitly requests cross-workspace routing. - **Reuse one helper pane.** Use an existing non-caller helper pane or create one on the right. Create the intended layout directly with `new-pane --type … --focus false`. - **Keep errors visible.** Never append `2>/dev/null`; stderr and exit status reveal invalid refs and flags. ## Inspect, read, and send
Details
- Skill name
cmux- Repository
- davidondrej/skills
- Path
skills/cmux/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Cmux skill do?
Control the cmux macOS terminal app: workspaces, panes, surfaces, browsers, notifications, settings, and hooks. Use only when the user explicitly names cmux. Read before running any cmux command.
How do I install the Cmux skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add davidondrej/skills --skill cmux. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cmux popular?
It lives in davidondrej/skills, which has 4,336 GitHub stars and 628 forks.
Related skills
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
4x4
4.3kdavidondrej/skills
Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.
Adr Verbatim
4.3kdavidondrej/skills
Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.
Domain Checker
4.3kdavidondrej/skills
Check domain registration in batches using public RDAP APIs, without keys or login. Use only when the user explicitly invokes /domain-checker.
Before Building
4.3kdavidondrej/skills
Fire the moment the user proposes a build. Instantly surface the 1-3 consequential choices hidden in their idea. Can also be invoked with /before-building.
Keep Track
4.3kdavidondrej/skills
Keep track of open topics and decisions. Use when the user says "keep-track" or asks to keep a running list of remaining items.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.