Skip to content
TrustedSkillsbeta
Back to all skills

Tmux Aware

Checked
sjungling·vlatest·other·MIT

This skill makes the AI aware of Tmux sessions, enabling it to interact within those environments for enhanced control and automation.

Repository

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 sjungling/sjungling-claude-plugins --skill tmux-aware -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

sjungling

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 sjungling/claude-plugins at 0dd093bc8c.

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

Commit
0dd093bc8c
Manifest
plugins/tmux-tools/skills/tmux-aware/SKILL.md
Scanned
2 files, 227 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 understand and interact with your Tmux sessions. It can list active windows, switch between them, send commands to specific panes, and generally manage your terminal multiplexer environment. This enables the agent to perform tasks within existing terminal workflows or even automate complex terminal-based processes.

When to use it

  • Automated server management: The agent can execute commands on a remote server managed through Tmux.
  • Workflow automation: Automate repetitive tasks that involve multiple terminal panes and windows.
  • Terminal-based development: The agent can assist with coding, debugging, or running tests within your existing Tmux setup.
  • Remote assistance: The agent can take over a user's Tmux session to help troubleshoot issues or perform specific actions.

Key capabilities

  • Listing active Tmux windows and panes
  • Switching between Tmux windows
  • Sending commands to individual Tmux panes

Example prompts

  • "List all my tmux windows."
  • "Send 'ls -l' to the pane in the 'dev' window."
  • "Switch to the last tmux window."

Tips & gotchas

  • Requires a running Tmux server. The agent will need appropriate permissions to interact with your Tmux environment.