skill-system-tmux

Route long-running shell commands through tmux sessions with oc- prefixes.

Updated Aug 23, 2026

Search Tags:#automation #devops #tmux #long-running #session-management #agent-tools

Ready to run

npx skills add https://github.com/arthur0824hao/ExperimentPipeline --skill skill-system-tmux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-system-tmux
Source: https://github.com/arthur0824hao/ExperimentPipeline/tree/main/.agents/skills/skill-system-tmux
Command: npx skills add https://github.com/arthur0824hao/ExperimentPipeline --skill skill-system-tmux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route shell commands through tmux when they risk timeout, require persistence, or need interactive terminal access. This skill provides decision heuristics and session management conventions — not tmux tutorials.

Core Features & Use Cases

Decision matrix to route commands between direct bash and tmux based on duration, interactivity, and persistence.
Enforced project-context session naming with oc- prefixes to enable bulk cleanup and safe multi-project operation.
Patterns for background tasks, persistent servers, readiness checks, and resource reclamation.

Quick Start

Start by routing a long-running build command to a tmux session named oc-build to ensure it persists across disconnects.

Frequently Asked Questions about skill-system-tmux

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

FAQPage Schema

How do I keep long-running shell commands from timing out during remote sessions?▼

To prevent long-running shell commands from timing out, route them through tmux sessions for persistent execution. This approach keeps tasks alive in the background, ensuring they survive disconnects and continue running safely without terminal interference.

When should I use tmux session management instead of running commands directly in bash?▼

Use tmux session management instead of direct bash when commands risk timeouts, require persistence, or need interactive terminal access. A decision matrix evaluates command duration, interactivity, and persistence needs to determine the correct routing.

How do I manage multiple tmux sessions for different projects without naming conflicts?▼

Manage multiple project tmux sessions by enforcing project-context session naming with oc- prefixes. This convention prevents naming conflicts, enables safe multi-project operation, and allows bulk cleanup to reclaim resources efficiently.

Can I run persistent servers and background tasks in tmux that survive SSH disconnects?▼

Yes, you can run persistent servers and background tasks in tmux that survive SSH disconnects. Routing remote executions through tmux ensures interactive sessions and long-running commands persist independently of the active SSH connection status.

What is the best way to clean up idle tmux sessions and reclaim system resources?▼

The best way to clean up idle tmux sessions and reclaim system resources is through a bulk cleanup workflow. By enforcing oc- prefixes for session naming, you can safely identify and terminate orphaned background tasks across multiple projects.

How do I perform readiness checks on background servers running inside tmux?▼

Perform readiness checks on background servers running inside tmux by applying specific session patterns. These patterns monitor persistent servers routed through tmux, verifying task completion and service availability before proceeding with downstream executions.