Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vellum-terminal-sessions
Manage persistent terminal sessions via tmux. Create, read, write to, list, and close named shell sessions.
Passed 15 of 20 test cases with the skill, and 11 of 20 without it.
and 2 more in the full report
5 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write out the exact single CLI invocation to print the last 50 lines of history from a tmux session named 'worker1' directly to stdout.
| Checked | Without skill | With skill |
|---|---|---|
| Uses tmux capture-pane -t worker1 -p -S -50 | Missed | Passed |
The instructions your model reads when the skill loads.
This skill manages persistent terminal sessions via tmux. Two modes:
| Sandbox Mode | Host Mode | |
|---|---|---|
| Where tmux runs | In the assistant's sandbox | On the user's host machine |
| How user connects | vellum terminal attach <session-name> | User opens their own terminal |
| Assistant access | Direct (bash tool) | Via host_bash |
| Best for | Long-running builds, servers, always-on tasks | Work needing host access (e.g. SwiftUI builds, host-local services) |
Default: Use Sandbox Mode unless the task specifically requires host access. Details: sandbox-sessions.md · host-sessions.md · tmux-best-practices.md
Sandbox Mode: No setup needed — tmux is available in the sandbox.
Host Mode: Requires tmux on the host — see host-sessions.md.
tmux list-sessions to get names and current commandstmux capture-pane -t NAME -p -S -50 (30-50 lines is usually enough)test cases passed, vs 11 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.