Official agent skill

Tmux Long Tasks

Use tmux to launch and manage long-running jobs that must survive beyond the bash tool timeout.

OfficialMITAuto-check passed

Install Tmux Long Tasks

skills CLI

$ npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops tmux-long-tasks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/action/tmux/tmux-long-tasks .claude/skills/tmux-long-tasks && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "tmux-long-tasks" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks into .claude/skills/tmux-long-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tmux-long-tasks", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops tmux-long-tasks --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/action/tmux/tmux-long-tasks .agents/skills/tmux-long-tasks && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "tmux-long-tasks" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks into .agents/skills/tmux-long-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tmux-long-tasks", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops tmux-long-tasks --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/action/tmux/tmux-long-tasks .cursor/skills/tmux-long-tasks && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "tmux-long-tasks" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks into .cursor/skills/tmux-long-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tmux-long-tasks", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/intel/torch-xpu-ops.git --path .claude/skills/action/tmux/tmux-long-tasks

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops tmux-long-tasks --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/action/tmux/tmux-long-tasks .gemini/skills/tmux-long-tasks && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "tmux-long-tasks" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks into .gemini/skills/tmux-long-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tmux-long-tasks", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install intel/torch-xpu-ops tmux-long-tasks

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/action/tmux/tmux-long-tasks .github/skills/tmux-long-tasks && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "tmux-long-tasks" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks into .github/skills/tmux-long-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tmux-long-tasks", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops tmux-long-tasks --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/action/tmux/tmux-long-tasks .opencode/skills/tmux-long-tasks && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "tmux-long-tasks" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/action/tmux/tmux-long-tasks into .opencode/skills/tmux-long-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tmux-long-tasks", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: tmux-long-tasks
GitHub stars: 115
Token cost: ~530 tokens
SKILL.md length: 169 words
Files: 1
Skills in repo: 29
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Use tmux to launch and manage long-running jobs that must survive beyond the bash tool timeout.

Works in 6 steps: Check tmux sessions → Create a window and launch the job → Verify the job started → …
The user mentions long-running commands
SKILL.md covers Required Inputs and Instructions
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tmux Long Tasks is an agent skill from intel/torch-xpu-ops, published by the product's own GitHub organization. Use tmux to launch and manage long-running jobs that must survive beyond the bash tool timeout. Use this skill when the user mentions long-running commands, background tasks, training jobs, large builds, or any command expected to exceed the bash tool timeout.

Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with tmux and Bash. The licence is MIT.

When your agent uses it

The user mentions long-running commands
Background tasks
Any command expected to exceed the bash tool timeout

Example prompts

“/tmux-long-tasks”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Check tmux sessions
Create a window and launch the job
Verify the job started
Check progress
Stop the job
Report to user

What it can do on your machine

Read from SKILL.md and the folder at commit a033aa5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tmux Long Tasks loads about 530 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 169 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~69
When it runs · the whole SKILL.md, loaded when a task matches: ~530

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from intel/torch-xpu-ops at commit a033aa5, republished under its MIT licence (© intel). 169 words, ~530 tokens.

Download SKILL.mdSave it as .claude/skills/tmux-long-tasks/SKILL.md (or your agent's skills folder).

name: tmux-long-tasks
description: Use tmux to launch and manage long-running jobs that must survive beyond the bash tool timeout. Use this skill when the user mentions long-running commands, background tasks, training jobs, large builds, or any command expected to exceed the bash tool timeout.
license: MIT
metadata.tmux: long-running jobs
metadata.bash: background tasks

Run Long Tasks with tmux

The bash tool kills all processes (including & and nohup) when it times out. Use tmux for any job that may exceed the timeout.

Do NOT use &, nohup, or shell backgrounding for long-running jobs.

Required Inputs

Before launching, you need:

tmux session name
Job/window name
Working directory
Command to run

If any are missing, ask the user and stop.

Instructions

Step 1: Check tmux sessions

bash

tmux list-sessions 2>/dev/null || echo "NO_TMUX_SESSIONS"

If tmux is not installed, stop and report.

If the target session does not exist, create it:

bash

tmux new-session -d -s <session>

Step 2: Create a window and launch the job

bash

tmux new-window -d -n <job_name> -t <session>
tmux send-keys -t <session>:<job_name> 'cd /work/dir || exit 1; CMD 2>&1 | tee run.log' Enter

Use cd <dir> || exit 1 (not &&) so failures are visible in pane output.

If a window with the same name already exists, append a suffix (e.g., _2).

Step 3: Verify the job started

bash

sleep 2
tmux capture-pane -p -t <session>:<job_name> | tail -5

If the shell prompt reappeared or an error is visible, the job failed immediately. Report to user.

Step 4: Check progress

bash

tmux capture-pane -p -t <session>:<job_name> | tail -20

For full history, use the log file:

bash

tail -20 /work/dir/run.log

Step 5: Stop the job

bash

tmux send-keys -t <session>:<job_name> C-c

Step 6: Report to user

After launching, report:

text

Job launched in tmux.
Session: <session> | Window: <job_name>
Log: <log_file>
Check: tmux capture-pane -p -t <session>:<job_name> | tail -20
Stop:  tmux send-keys -t <session>:<job_name> C-c

Files

Just SKILL.md in .claude/skills/action/tmux/tmux-long-tasks of intel/torch-xpu-ops.

Open the folder on GitHubat commit a033aa5

Compare with similar skills

Tmux Long Tasks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tmux Long Tasks compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Tmux Long Tasks this skillintel/torch-xpu-ops	115	—	~530	Automated safety check: Pass	MIT	today
Teamethanhq/cc-fleet	215	1 repos	~3.4k	Automated safety check: Pass	Apache-2.0	9 days ago
Tmuxsickn33/agentic-awesome-skills	47k	2 repos	~2.8k	Automated safety check: Pass	MIT	yesterday
Tmux Runmeain/dotfiles	285	—	~1.4k	Automated safety check: Pass	MIT	1 mo ago
Tmux CLIsammcj/agentic-coding	162	—	~923	Automated safety check: Pass	Apache-2.0	today
Dotfiles Managereinverne/dotfiles	121	—	~1.3k	Automated safety check: Notes	GPL-3.0	29 days ago

Similar skills

Team
ethanhq/cc-fleet
Spawn long-lived provider LLM teammates in tmux panes that you message via the native agent-team tools — multi-turn, collaborative, watchable.
215 GitHub starsUsed in 1 repo~3.4k tokens
Agent WorkflowsAuto-check passed
Tmux
sickn33/agentic-awesome-skills
Expert tmux session, window, and pane management for terminal multiplexing, persistent remote workflows, and shell scripting automation.
47k GitHub starsUsed in 2 repos~2.8k tokens
DevelopmentAuto-check passed
Tmux Run
meain/dotfiles
Run a command in a tmux pane/window/session and monitor its output for errors.
285 GitHub stars~1.4k tokensUpdated 1 mo ago
Auto-check passed
Tmux CLI
sammcj/agentic-coding
CLI utility to help when running ongoing interactive CLI sessions or using tmux to communicate with other CLI Agents.
162 GitHub stars~923 tokensUpdated today
Auto-check passed
Dotfiles Manager
einverne/dotfiles
Comprehensive knowledge of dotfiles management, configuration file organization, symlink strategies, and cross-platform environment setup.
121 GitHub stars~1.3k tokensUpdated 29 days ago
Productivity & AutomationAuto-check: notes
Tmux Layout
majiayu000/claude-skill-registry
A skill your agent uses when the operator wants a prepared tmux visualization layout for the session's side-channels (STATE.md tail, CI-watch, events.jsonl tail).
666 GitHub starsUsed in 1 repo~1.6k tokens
DevOps & CloudAuto-check passed

More from intel/torch-xpu-ops

All 29 skills in this repo

Intel GPU Device Selection
intel/torch-xpu-ops
Official
Select the Intel GPU device to use when a system has multiple Intel GPU devices.
115 GitHub stars~508 tokensUpdated today
Auto-check passed
Xpu CI Health Check
intel/torch-xpu-ops
Official
Check PyTorch ciflow/xpu (xpu.yml) on the main branch, collect the failing XPU test cases from the most recent completed run(s), analyze the ROOT CAUSE of each failure with AI, and produce a list…
115 GitHub stars~1.5k tokensUpdated today
Auto-check passed
At Dispatch V2
intel/torch-xpu-ops
Official
Convert PyTorch ATDISPATCH macros to ATDISPATCHV2 format in ATen C++ code.
115 GitHub starsUsed in 3 repos~2.2k tokens
Auto-check passed
PR Review
intel/torch-xpu-ops
Official
Review pull requests for XPU operator or backend code. An agent skill from intel/torch-xpu-ops.
115 GitHub stars~4.2k tokensUpdated today
Auto-check passed
Skill Writer
intel/torch-xpu-ops
Official
Guide users through creating Agent Skills for Claude Code. An agent skill from intel/torch-xpu-ops.
115 GitHub starsUsed in 3 repos~2.4k tokens
Auto-check passed
Ut Issue Authoring
intel/torch-xpu-ops
Official
Read the evidence a nightly UT run produced, decide which failures share a root cause and which are machine breakage rather than product bugs, and write one issue draft per root cause to drafts.json.
115 GitHub stars~2k tokensUpdated today
Auto-check passed

Works with

Questions about Tmux Long Tasks

What does Tmux Long Tasks do?

Use tmux to launch and manage long-running jobs that must survive beyond the bash tool timeout. Tmux Long Tasks is an agent skill from intel/torch-xpu-ops, published by the product's own GitHub organization. Use tmux to launch and manage long-running jobs that must survive beyond the bash tool timeout.

When should I use Tmux Long Tasks?

Tmux Long Tasks fits situations like: the user mentions long-running commands; background tasks; any command expected to exceed the bash tool timeout.

How do I install Tmux Long Tasks in Claude Code?

Run `npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a claude-code`. Or copy the skill folder (.claude/skills/action/tmux/tmux-long-tasks in intel/torch-xpu-ops) into .claude/skills/tmux-long-tasks in your project. Claude Code loads it when a task matches its description.

How do I install Tmux Long Tasks in Codex?

Run `npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a codex`. Or copy the skill folder (.claude/skills/action/tmux/tmux-long-tasks in intel/torch-xpu-ops) into .agents/skills/tmux-long-tasks in your project. Codex loads it when a task matches its description.

Can I use Tmux Long Tasks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intel/torch-xpu-ops --skill tmux-long-tasks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tmux-long-tasks, .gemini/skills/tmux-long-tasks, .github/skills/tmux-long-tasks and .opencode/skills/tmux-long-tasks in your project.

What does Tmux Long Tasks need to run?

SKILL.md names no scripts, command-line tools or credentials: Tmux Long Tasks is instructions for the agent only.

Does Tmux Long Tasks access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tmux Long Tasks safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tmux Long Tasks use?

Tmux Long Tasks is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tmux Long Tasks use?

About 530 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tmux Long Tasks?

Skills that share tags, products or a category with Tmux Long Tasks: Team (ethanhq/cc-fleet, 215 stars), Tmux (sickn33/agentic-awesome-skills, 47k stars), Tmux Run (meain/dotfiles, 285 stars) and Tmux CLI (sammcj/agentic-coding, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tmux Long Tasks?

intel (a GitHub organization, an official publisher) maintains it in intel/torch-xpu-ops, which has 115 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.

Source: intel/torch-xpu-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Tmux Long Tasks

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Run Long Tasks with tmux

Required Inputs

Instructions

Step 1: Check tmux sessions

Step 2: Create a window and launch the job

Step 3: Verify the job started

Step 4: Check progress

Step 5: Stop the job

Step 6: Report to user

Files

Compare with similar skills

Similar skills

More from intel/torch-xpu-ops

Related

Questions about Tmux Long Tasks