Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/tmux-processes
Patterns for running long-lived processes in tmux.
Passed 22 of 22 test cases with the skill, and 9 of 22 without it.
and 11 more in the full report
13 fixed9 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Give me the exact terminal command to dump the last 50 lines from a window named 'logs' in session 'myapp' directly to standard output.
| Checked | Without skill | With skill |
|---|---|---|
| Uses tmux capture-pane -p -t myapp:logs -S -50. | Missed | Passed |
The instructions your model reads when the skill loads.
Use send-keys pattern for reliable shell initialization. Creating a session spawns an interactive shell automatically. Use send-keys to run commands within that shell, ensuring PATH, direnv, and other initialization runs properly.
# WRONG - inline command bypasses shell init, breaks PATH/direnv
tmux new-session -d -s "$SESSION" -n main 'tilt up'
# CORRECT - create session, then send command to interactive shell
tmux new-session -d -s "$SESSION" -n main
tmux send-keys -t "$SESSION:main" 'tilt up' Enter
Always derive session name from the project:
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
For multiple processes in one project, use windows not separate sessions:
myappserver, tests, logsSESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Create session with named window, then send command
tmux new-session -d -s "$SESSION" -n main
tmux send-keys -t "$SESSION:main" '<command>' Enter
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.