pk-tmux

Automate project-scoped tmux session creation, status, and attach via Unix sockets.

1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/caseneuve/dotclaude --skill pk-tmux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pk-tmux
Source: https://github.com/caseneuve/dotclaude/tree/main/claude/skills/pk-tmux
Command: npx skills add https://github.com/caseneuve/dotclaude --skill pk-tmux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, and includes scripts (resource) components.

## What problem does it solve? This skill simplifies the management of per-project tmux sessions by providing a consistent, script-driven approach to create, monitor, and attach to sessions via Unix sockets in /tmp.

## Core Features & Use Cases

  • Session lifecycle management: create, verify, and attach to a tmux session with a standard socket path per project.
  • Status and window visibility: report active windows, their CWDs, and whether a pane is actively running a command.
  • Workflow automation: initialize sessions, spawn windows for tasks, send commands, and poll for completion.
  • Use case: on a development project, initialize a persistent session, run a long-running server in a dedicated window, and monitor progress. ### Quick Start Initialize a session with tmux-create.sh and attach to it using the provided attach command.

Frequently Asked Questions about pk-tmux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tmux session management for multiple development projects?

You can automate tmux session management by using shell scripts to create, verify, and attach to persistent project sessions via Unix sockets in /tmp. This provides a consistent, script-driven approach to orchestrating windows and background tasks.

What is the best way to run and monitor long-running background tasks in a persistent terminal?

The best way to monitor long-running background tasks is to initialize a persistent tmux session, spawn a dedicated window for the server task, send commands, and use a polling script to wait for completion while tracking active panes.

Do I need tmux installed locally to use project-scoped terminal session automation?

Yes, tmux is a required dependency. You need it installed locally to run the shell-based scripts that manage session lifecycles, standard socket paths per project, and window orchestration.

Can I check the status of active windows and running commands in a tmux session?

Yes, you can check session status by running a status script that reports active windows, their current working directories, and whether a specific pane is actively running a command.

How does a script-driven tmux session manager handle socket paths for different projects?

A script-driven tmux session manager handles socket paths by assigning a standard Unix socket file in the /tmp directory for each project. This isolates project sessions and allows reliable creation and attachment.

Why use Unix sockets in /tmp for persistent terminal sessions instead of default tmux management?

Using Unix sockets in /tmp provides a standardized, per-project socket path for reliable session creation and status polling. This ensures persistent terminal workflows remain organized across multiple concurrent projects.