.agents/skills/tmux/SKILL.md
Instructions for using tmux to spawn multiple processes, inspect them, and capture their output. Use when running servers, long-running tasks, or background processes.
npx skillsauth add colmarius/dot-agents tmuxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage background processes using tmux windows without blocking the terminal.
Confirm tmux is running and list existing windows:
tmux list-windows
Create a new tmux window and run a command:
tmux new-window -n "my-server" -d
tmux send-keys -t "my-server" "npm run dev" C-m
-n "my-server" names the window for easy reference-d keeps it detached (runs in background)C-m sends Enter to execute the commandtmux capture-pane -p -t "my-server"
tmux capture-pane -p -t "my-server" -S -1000
-S -1000 captures the last 1000 lines of scrollbacktmux send-keys -t "my-server" C-c
tmux kill-window -t "my-server"
Run multiple commands in sequence:
tmux new-window -n "build" -d && \
tmux send-keys -t "build" "npm run build && npm run test" C-m
| Action | Command |
| ------ | ------- |
| Create window | tmux new-window -n "ID" -d |
| Run command | tmux send-keys -t "ID" "CMD" C-m |
| Read output | tmux capture-pane -p -t "ID" |
| Send interrupt | tmux send-keys -t "ID" C-c |
| Kill window | tmux kill-window -t "ID" |
development
Deep research on technical topics, libraries, APIs, or concepts. Use when asked to research, investigate, explore deeply, or gather comprehensive information on a topic. Saves learnings to .agents/research/.
development
Autonomous multi-iteration feature implementation using handoff loops. Use when asked to "run ralph", "execute autonomously", "implement this plan autonomously", or for hands-free feature development from structured plans.
data-ai
Analyze project and fill in AGENTS.md. Use when adapting dot-agents to a new project, after initial installation.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.