tmux

Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, highly executable reference that teaches tmux by example without padding. Sequences are clear and validation appears in the build pattern, though no formal error-recovery loop is documented.

Suggestions

Add a brief note on how to detect and recover from a failed build (e.g. inspect /tmp/build.log and re-run after fixing) to reach the top workflow_clarity anchor.

Clarify how to check whether a session is still alive (e.g. `tmux has-session -t build`) alongside the list-sessions/capture-pane checks.

Dimension	Reasoning	Score
Conciseness	The body is lean: it assumes tmux knowledge, leads with executable commands and brief inline comments, and avoids explaining what tmux or shell sessions are.	5 / 5
Actionability	Every section gives copy-paste-ready commands (new-session, list-sessions, capture-pane, send-keys, kill-session) and two complete worked patterns covering the common build/tail cases.	5 / 5
Workflow Clarity	The build pattern shows a clear start-then-check sequence with an explicit exit-flag checkpoint, but there is no error-recovery feedback loop, so it sits just below the top anchor.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references, the skill is organized into clearly labeled sections (start/check/send/end/patterns/when-not-to), which is ideal for a simple single-purpose skill.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A crisp, third-person description that concretely states capabilities and gives explicit, natural-language trigger guidance. It is distinguishable and avoids fluff or over-claims.

Dimension	Reasoning	Score
Specificity	"start a detached session, run a long task, reattach later, capture output" lists four concrete, distinct actions with comprehensive coverage of tmux's core capability surface.	5 / 5
Completeness	It explicitly answers what ("start a detached session, run a long task, reattach later, capture output") and when ("Use when a task takes longer than a single tool call (build, test, log tail)") with concrete triggers.	5 / 5
Trigger Term Quality	"build, test, log tail" and "long-running" are natural phrases users say, but a few common synonyms (e.g. "background process", "long-running command") are absent.	4 / 5
Distinctiveness Conflict Risk	"Manage long-running shell sessions with tmux" carves a clear niche with distinct triggers (tmux, detached sessions, build/test/log tail) and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Team-Commonly/commonly
Path: backend/commonly-bundled-skills/tmux/SKILL.md
Commit: e701dba

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.