/tmux-cli
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
$ npx -y skills add pchalasani/claude-code-tools --skill tmux-cli --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/tmux-cli
Context preview
The summary Claude sees to decide when to auto-load this skill.
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
SKILL.md
tmux-cli.SKILL.mdname: tmux-cli description: CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
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:
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 timeoutThis 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.
Practical productivity tools for Claude Code, Codex-CLI, and similar CLI coding agents.
Repo: pchalasani/claude-code-tools
Other skills on claude-code-tools.
- /recover-context
Extract full context of the last task from the most recent parent session
Open skill - /session-search
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Open skill - /dynamic-workflow
Create, review, run, inspect, pause, resume, and cancel durable JavaScript workflows that coordinate multiple headless Codex agents. Use for dynamic fan-out and fan-in, per-item analysis, multi-stage agent pipelines, loops or branches driven by worker results, long background
Open skill - /add-pattern
Use this skill when you learn one or more design pattern(s) in the
Open skill - /patterns
Design patterns for the Langroid multi-agent LLM framework. Covers
Open skill - /msg
Inter-agent communication via the msg CLI. Use this when you need to send messages to other agent sessions, read incoming messages, or coordinate with other agents in tmux panes.
Open skill

