Skip to content
TrustedSkillsbeta
Back to all skills

Tmux

Checked
mitsuhiko·vlatest·productivity·Apache-2.0

Tmux allows you to manage multiple terminal sessions within a single window, boosting productivity and remote work efficiency.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mitsuhiko/agent-stuff --skill tmux -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mitsuhiko

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mitsuhiko/agent-commands at 0865c849be.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 295 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows an AI agent to interact with and manage terminal sessions using tmux. It enables creating, listing, attaching to, detaching from, and killing tmux sessions programmatically. This provides a way for agents to automate terminal workflows and manage complex tasks requiring multiple terminals.

When to use it

  • Automating server administration tasks that require managing multiple terminal windows.
  • Creating reproducible development environments by scripting the setup of tmux sessions.
  • Running long-running processes in detached tmux sessions, even after the agent disconnects.
  • Managing remote shell connections and workflows within a consistent environment.

Key capabilities

  • Create new tmux sessions
  • List existing tmux sessions
  • Attach to an existing session
  • Detach from a session
  • Kill a tmux session

Example prompts

  • "Create a new tmux session named 'dev_env'."
  • "List all running tmux sessions."
  • "Attach to the tmux session called 'production'."
  • "Kill the tmux session named 'test_server'."

Tips & gotchas

Requires tmux to be installed on the system where the agent is operating. The agent needs appropriate permissions to manage tmux sessions, which may require sudo access depending on the configuration.