agentleFS
nikshipsnikships/skills-registry/.agents/skills/cmux/SKILL.md

cmux

Skill25 starsChanged 6 months agoApache-2.0View on GitHub

End-user control of cmux topology and routing (windows, workspaces, panes/surfaces, focus, moves, reorder, identify, trigger flash). Use when automation needs deterministic placement and navigation in a multi-pane cmux layout.

27 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use cmux-browser, cmux-markdown and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • manaflow-aiSkill

    cmux-browser

    Automate the browser inside cmux. Use for cmux browser, browser surface, webview, current workspace browser, snapshot refs, DOM actions, waits, screenshots, cookies, storage, tabs, downloads, console, errors, and browser session state.

    Also in 4 projects that use this

  • basicmachines-coSkill

    cmux-markdown

    Open markdown files in a formatted viewer panel with live reload. Use when you need to display plans, documentation, or notes alongside the terminal with rich rendering (headings, code blocks, tables, lists).

    Also in 3 projects that use this

  • basicmachines-coSkill

    cmux-settings

    View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences (appearance, sidebar, notifications, automation, browser, shortcuts), set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux recognizes. Triggers on '/cmux-settings', 'change cmux setting', 'set <something> in cmux', 'cmux config', 'cmux.json', or 'rebind a cmux shortcut'.

    Also in 3 projects that use this

  • manaflow-aiSkill

    cmux-workspace

    Work inside the current cmux workspace and terminal. Use for cmux workspace, current workspace, caller surface, panes, surfaces, tagged reloads, socket targeting, and non-interfering cmux automation.

    Also in 3 projects that use this

  • matyasstochSkill

    effective-agent-skills

    How to write effective agent skills — what to do, what not to do, anatomy, progressive disclosure, design patterns, anti-patterns, testing, security. Read this whenever a skill (Claude Skill, Agent Skill, SKILL.md) is being created, edited, reviewed, or debugged. Use when the user says "create a skill", "new skill", "update this skill", "improve a skill", "why isn't my skill triggering", or anything else involving authoring or editing SKILL.md files.

    Also in 3 projects that use this

  • itgoyoSkill

    browser-harness

    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.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to control non-browser cmux topology and routing.

    line 8
  2. Very specific:

    Use cmux docs settings before changing cmux-owned settings.

    line 42
  3. Distinctive:

    Use cmux settings for app behavior, sidebar, notifications, browser behavior, automation, workspace colors, and cmux-owned shortcuts.

    line 55
  4. Very specific:

    Default output uses short refs: window:N, workspace:N, pane:N, surface:N.

    line 67

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

cmux Core Control

Use this skill to control non-browser cmux topology and routing.

Core Concepts

  • Window: top-level macOS cmux window.
  • Workspace: tab-like group within a window.
  • Pane: split container in a workspace.
  • Surface: a tab within a pane (terminal or browser panel).

Fast Start

# identify current caller context
cmux identify --json

# list topology
cmux list-windows
cmux list-workspaces
cmux list-panes
cmux list-pane-surfaces --pane pane:1

# create/focus/move
cmux new-workspace
cmux new-split right --panel pane:1
cmux move-surface --surface surface:7 --pane pane:2 --focus true
cmux split-off --surface surface:7 right
cmux reorder-surface --surface surface:7 --before surface:3

# attention cue
cmux trigger-flash --surface surface:7

Settings and Docs

Use cmux docs settings before changing cmux-owned settings. It prints the docs URL, schema URL, raw GitHub resources, cmux.json paths, and reload command.

cmux docs settings
cmux settings path

cmux-owned settings live in ~/.config/cmux/cmux.json. Legacy ~/.config/cmux/settings.json and ~/Library/Application Support/com.cmuxterm.app/settings.json files are read only as fallback for missing keys. Before editing, copy any existing cmux.json file to a timestamped .bak next to it so the user can revert. Edit the user file, then reload:

cmux reload-config

Use cmux settings for app behavior, sidebar, notifications, browser behavior, automation, workspace colors, and cmux-owned shortcuts. Terminal rendering settings such as font, cursor style, theme, and scrollback belong in Ghostty config.

Open the UI when useful:

cmux settings
cmux settings cmux-json
cmux settings shortcuts

Handle Model

  • Default output uses short refs: window:N, workspace:N, pane:N, surface:N.
  • UUIDs are still accepted as inputs.
  • Request UUID output only when needed: --id-format uuids|both.

Deep-Dive References

ReferenceWhen to Use
references/handles-and-identify.mdHandle syntax, self-identify, caller targeting
references/windows-workspaces.mdWindow/workspace lifecycle and reorder/move
references/panes-surfaces.mdSplits, surfaces, move/reorder, focus routing
references/trigger-flash-and-health.mdFlash cue and surface health checks
../cmux-browser/SKILL.mdBrowser automation on surface-backed webviews
../cmux-markdown/SKILL.mdMarkdown viewer panel with live file watching

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.