Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
SkillScore100Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/20/2026
What it changes
Passed 19 of 19 test cases with the skill, and 7 of 19 without it.
Without skill36%
With skill100%
Checks it passed that the model alone missed
Returns the captured log lines from the tmux pane buffer.
Contains the top process list scraped from the htop tmux pane.
Returns the redis key query results scraped from the tmux pane.
and 20 more in the full report
14 fixed8 passed either way0 still failing0 broke
Pass-rate lift
+64 pp
Tokens
+14%
Agent turns
0%
Response time
-21%
Model gemini-3.6-flashMeasured 8/20/2026v122 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
An `ipython` shell is active in tmux pane `ipython:0.0`. Send `%history -n 1-5` to list the first 5 input commands, scrape the pane screen, and return the history output with action notes.
What was checked, without and with the skill
Checked
Without skill
With skill
Contains the command history output scraped from the ipython tmux pane.
Missed
Passed
Includes action notes describing the command sent to ipython.
Passed
Passed
case-22 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md33 lines3 filesincludes scripts
Tmux
Purpose
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Routing
Use when: Use when the user asks to remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Avoid using in non-interactive environments unless automation can fully satisfy prompts.
Outputs: Outcome from Tmux: task-specific result plus concrete action notes.
Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
Use the tmux skill for this request.
Help me with tmux.
Use when the user asks to remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Tmux: provide an actionable result.
Negative
Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Avoid using in non-interactive environments unless automation can fully satisfy prompts.
Do not use tmux for unrelated requests.
This request is outside tmux scope.
This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
Current runtime prompt length: 3942 characters.
Runtime prompt is defined directly in ../tmux.json.