CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

Excellent operational content: fully executable commands, a lifecycle-ordered structure, and an explicit validation feedback loop in the common patterns, with no filler or tutorial padding. The single minor gap is that the file is slightly past the compact threshold where a patterns reference file would improve organization.

DimensionReasoningScore

Conciseness

The body is lean: the only prose is environment-specific knowledge Claude cannot infer ('tmux is on PATH in the gateway', 'Sessions persist across tool-call boundaries … next heartbeat'), and it never explains what tmux is or how it works. Every code comment is load-bearing (e.g., 'note: end with C-m for Enter'), matching the 5-anchor's 'every token earns its place'.

5 / 5

Actionability

Every code block is complete and copy-paste executable — 'tmux new-session -d -s build "npm run build > /tmp/build.log 2>&1"', 'tmux capture-pane -t build -p -S -1000', 'tmux send-keys -t build … C-m' — and the two 'Common patterns' cover the dominant use cases (build with exit flag, non-blocking log tail) with a ready-to-run polling check. This matches the 5-anchor with no gaps in the common cases.

5 / 5

Workflow Clarity

The sections sequence the session lifecycle (start → check → send input → end), and the 'Long-running build with status flag' pattern includes an explicit validation checkpoint with a feedback branch ('if [ -f /tmp/build.exit ] … else … Build still running…'), matching the 5-anchor's 'explicit validation steps; feedback loops'. No destructive or batch operation lacks verification.

5 / 5

Progressive Disclosure

A well-organized, self-contained single file with clear sections ('Start a detached session', 'Check on a session', 'Send input', 'End a session', 'Common patterns', 'When NOT to use tmux') and no external references needed. At ~75 lines it sits just past the compact (<50 line) threshold where the 'Common patterns' recipes could be split into a reference file — a minor organization gap matching anchor 4 ('most content is appropriately placed; minor organization gaps') rather than 5.

4 / 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 strong description that cleanly answers both what the skill does and when to use it, with four concrete lifecycle actions and natural trigger phrases anchored by the tmux name. The only weakness is modest synonym coverage in its trigger terms (e.g., no 'background' phrasing).

DimensionReasoningScore

Specificity

The description lists four concrete actions — 'start a detached session, run a long task, reattach later, capture output' — covering the full session lifecycle, matching the 5-anchor's breadth (four named actions, comprehensive). The omitted capabilities (send-keys, kill-session) sit below description altitude and don't constitute the 'minor gaps' of anchor 4.

5 / 5

Completeness

Both questions are explicitly answered: a clear 'what' ('Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output') followed by an explicit 'Use when a task takes longer than a single tool call (build, test, log tail)' with concrete triggers — the exact 5-anchor pattern, not the 4-anchor's less-specific 'when'.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — 'build, test, log tail', 'long-running', 'reattach', 'tmux' — giving good keyword coverage, but common synonyms a user might say ('background task', 'keep it running') are missing, matching anchor 4 ('a few natural terms missing') rather than the 5-anchor's synonym-level breadth.

4 / 5

Distinctiveness Conflict Risk

Naming 'tmux' plus the specific trigger condition ('a task takes longer than a single tool call') carves a clear niche with distinct triggers and minimal risk of firing for the wrong skill, matching the 5-anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

Team-Commonly/commonly

Path

backend/commonly-bundled-skills/tmux/SKILL.md

Reviewed

Table of Contents

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.