tmux-cli
The tmux-cli Claude Code skill enables inter-process communication with other CLI agents or scripts running in separate tmux panes. Use it to execute shell commands in other panes with exit code detection, send messages to running agents, or capture output from concurrent processes when orchestrating multi-agent workflows or complex automation tasks requiring coordination across multiple terminal sessions.
git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/tmux-cli && cp -r /tmp/tmux-cli/plugins/tmux-cli/skills/tmux-cli ~/.claude/skills/tmux-cliSKILL.md
# tmux-cli
## Instructions
Use the `tmux-cli` command to communicate with other CLI Agents or Scripts in
other tmux panes. Do `tmux-cli --help` to see how to use it!
This command depends on installing the `claude-code-tools`. If you get an error
indicating that the command is not available, ask the user to install it using:
`uv tool install claude-code-tools`.
## Key Commands
### Execute with Exit Code Detection
Use `tmux-cli execute` when you need to know if a shell command succeeded or
failed:
```bash
tmux-cli execute "make test" --pane=2
# Returns JSON: {"output": "...", "exit_code": 0}
tmux-cli execute "npm install" --pane=ops:1.3 --timeout=60
# Returns exit_code=0 on success, non-zero on failure, -1 on timeout
```
This is useful for:
- Running builds and knowing if they passed
- Running tests and detecting pass/fail
- Multi-step automation that should abort on failure
**Note**: `execute` is for shell commands only, not for agent-to-agent chat.
For communicating with another Claude Code instance, use `send` + `wait_idle` +
`capture` instead.Use this skill when you learn one or more design pattern(s) in the
Literature-backed English technical-prose writing rules (agent-style, 21 rules). Its lane is FORMAL technical prose (papers, design docs, proposals, READMEs, commit messages). Use ONLY when the user explicitly asks for agent-style by name (e.g. "apply agent-style", "write/revise this per agent-style rules", "iterate until agent-style clean"). NOT for de-AI-ing casual or voiced text — use remove-ai-patterns for that. Do not auto-trigger for ordinary prose or documentation tasks.
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
>-
>-
Log the work segment that you did after the last work log until now in a
Create a markdown document that describes a specific task along with