Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

tmux-awaretmux aware 搜索

Agent Skill

tmux-aware 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

346

周安装

14

GitHub Stars

11

下载量

109
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:tmux-aware(tmux aware 搜索)
来源仓库:https://github.com/sjungling/claude-plugins
仓库路径:skills/tmux-aware
安装命令:
npx skills add https://github.com/sjungling/claude-plugins --skill tmux-aware
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sjungling/claude-plugins --skill tmux-aware

简介

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于需要根据关键词或任务场景从来源线索中获取信息的场景。
  • 通过 npx skills add 命令安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态及是否触发联网或文件读写操作。
  • tmux-aware 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

TMUX-Aware Process Management

Overview

When running inside a TMUX session, manage services in dedicated panes without cluttering the current view. All Claude-created panes go in a dedicated "claude-controlled" window.

For the visual workflow diagram, see ./references/workflow.mmd.

Key Principles

  1. Never clutter the current window - Always create panes in the "claude-controlled" window
  2. Find panes by name - Search for existing panes/windows by title, not by process
  3. Verify commands worked - Capture output after sending commands to detect errors
  4. Ask when uncertain - If a pane can't be found by name, list options and ask the user

Starting a Service

When the user asks to start a service (e.g., "start the API server"):

Step 1: Check for claude-controlled window

# List windows, look for claude-controlled
tmux list-windows -F '#{window_index}:#{window_name}' | grep ':claude-controlled$'

Step 2: Create window if needed

# Create the claude-controlled window
tmux new-window -n "claude-controlled"

Step 3: Create a named pane for the service

# If claude-controlled window already has panes, split it
tmux split-window -t claude-controlled -v

# Name the pane after the service
tmux select-pane -t claude-controlled -T "api-server"

Step 4: Send the start command

tmux send-keys -t "claude-controlled:0.api-server" "npm run dev" Enter

Step 5: Verify it started (capture output after brief delay)

sleep 2
tmux capture-pane -t "claude-controlled:0.api-server" -p -S -20

Check the output for errors. Report success or detected issues.

Naming Convention

  • Window: claude-controlled (all Claude-created panes go here)
  • Pane titles: Lowercase, hyphenated, match the service (e.g., api-server, redis, vite-dev, postgres)

Finding Existing Panes

When the user asks to interact with a process (e.g., "check the redis logs"):

Step 1: List panes with names

tmux list-panes -a -F '#{window_name}:#{pane_index}:#{pane_title}'

Step 2: Search for match

Look for exact or partial match (e.g., "redis" matches pane titled "redis" or "redis-server").

Step 3: If found

Interact with it:

# Capture output
tmux capture-pane -t "window:pane" -p -S -50

# Send command (e.g., restart)
tmux send-keys -t "window:pane" C-c  # Stop first
tmux send-keys -t "window:pane" "redis-server" Enter  # Restart

Step 4: If not found

List available panes and ask:

I couldn't find a pane named 'redis'. Here's what I see: - [0:main] pane 0: "zsh" - [1:dev] pane 0: "vim" - [2:claude-controlled] pane 0: "api-server" Which one should I use, or should I create a new one?

Capturing Output

Use capture-pane to read recent output:

# Last 50 lines
tmux capture-pane -t "pane-target" -p -S -50

# Last 100 lines (for more context)
tmux capture-pane -t "pane-target" -p -S -100

Error Detection

After sending commands, capture output and look for common error patterns:

  • Error:, ERROR, error:
  • Exception, exception
  • Failed, FAILED, failed
  • Cannot, cannot
  • Exit codes in prompts
  • Stack traces

Report issues proactively: "Started the server but detected an error: [snippet]"

Stopping a Service

# Send Ctrl+C to stop
tmux send-keys -t "pane-target" C-c

# Verify it stopped
sleep 1
tmux capture-pane -t "pane-target" -p -S -10

Multiple Services

When running multiple services:

  • Split panes vertically (-v) for side-by-side logs
  • Name each pane after its service for easy targeting
  • Use tmux select-layout -t claude-controlled even-vertical to rebalance
  • If more than 3 services, consider separate windows instead of more pane splits

For the full command reference (window/pane management, sending commands, capturing output, target syntax), see ./references/commands.md.

Example Workflow

User: "Start a Redis server"

  1. Check for claude-controlled window (exists)
  2. Create new pane: tmux split-window -t claude-controlled -v
  3. Name it: tmux select-pane -T "redis"
  4. Start Redis: tmux send-keys -t "claude-controlled:redis" "redis-server" Enter
  5. Wait and capture: sleep 2 && tmux capture-pane -t "claude-controlled:redis" -p -S -20
  6. Report: "Started Redis server in pane 'redis' (claude-controlled window). Server is ready on port 6379."

User: "Check if Redis is still running"

  1. List panes, find "redis"
  2. Capture output: tmux capture-pane -t "claude-controlled:redis" -p -S -30
  3. Report status based on output

When NOT to Use

  • One-off commands that don't need a persistent pane (e.g., git status, ls)
  • User's existing layout - don't create panes in the user's current window
  • Non-tmux environments - if tmux detection fails, fall back to standard Bash
  • Quick checks where capturing output with Bash tool is sufficient

Cleanup

When the user's task is complete:

  • Don't auto-kill panes - the user may want to keep services running
  • Offer cleanup if asked: tmux kill-window -t claude-controlled
  • Report what's running: List active panes so the user can decide
  • If you started a service and the task failed, mention the pane is still running

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.57%
按下载量换算42

Claude

27.45%
按下载量换算30

Cursor

17.72%
按下载量换算19

Gemini CLI

9.57%
按下载量换算10

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills