tmux

Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tmux/SKILL.md

Quality

Content

78%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 tight, command-first reference with genuinely useful operational guidance (the -l/-- split, prompt-check-before-approve) and well-structured deferral to real helper scripts. Weaknesses are confined to minor gaps: no paste example, no helper invocation syntax, and an irrelevant migration-note section that spends tokens without aiding use.

Suggestions

Remove or relocate the "PilotDeck Migration Note" section — it is review/migration metadata with no value when the skill is invoked.

Add one-line invocation examples for the helper scripts (e.g. `scripts/wait-for-text.sh -t worker-3 "proceed"`) so they are immediately usable.

Include a paste-buffer example (e.g. `tmux set-buffer -- "text"; tmux paste-buffer -t shared:0.0`) to back the "paste text" capability claimed in the description, and note re-capturing the pane to verify input took effect.

Dimension	Reasoning	Score
Conciseness	The body is lean — nearly every line is an executable command with minimal prose, and it never explains what tmux is. However, the "PilotDeck Migration Note" section is review metadata irrelevant to using the skill, and a couple of Notes lines are marginal, so it falls just short of anchor 5's 'every token earns its place'.	4 / 5
Actionability	Commands are copy-paste ready and cover the common cases (list, capture with scrollback, send-keys with -l, special keys, prompt grep patterns). Minor gaps: the description promises "paste text" but no paste-buffer example appears, and the two helper scripts are named without an invocation example, matching anchor 4 rather than 5.	4 / 5
Workflow Clarity	The Prompt checks section gives a clear sequence — capture, grep for prompt markers, "Approve/select only when the prompt is understood", then send keys — an explicit checkpoint. It is not 5 because kill-session and other consequential operations lack verification steps, and there is no guidance to re-check output after sending input.	4 / 5
Progressive Disclosure	Structure is clean: short sections, core commands inline, and the two real bundle scripts (scripts/find-sessions.sh, scripts/wait-for-text.sh) deferred to a clearly signaled Helpers section one level deep, each with a one-line purpose. No buried references or content that belongs in a separate file, matching anchor 5.	5 / 5
	Total	17 / 20 Passed

Description

70%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 concise, concrete, third-person description with good trigger terms and a distinct tmux niche. Its main weakness is the complete absence of a 'when to use' clause, which caps completeness and leaves triggering to keyword inference alone.

Suggestions

Append an explicit trigger clause, e.g. "Use when working with existing interactive tmux sessions, driving terminal CLIs, or when the user mentions tmux, panes, or capturing terminal output."

Include a few natural synonyms or variants (e.g. "attach", "scrollback", "terminal multiplexer") to broaden trigger term coverage.

Mention session lifecycle operations (create/kill/rename) so the stated capability coverage matches what the skill body actually teaches.

Dimension	Reasoning	Score
Specificity	The description lists five concrete actions ("list, capture output, send keys, paste text, monitor prompts") for a named domain (tmux sessions/panes), but session management (new/kill/rename) is missing from the coverage. This matches anchor 4 ('several specific actions; minor gaps') rather than 5, which requires comprehensive coverage.	4 / 5
Completeness	The "what" is clear (control tmux sessions/panes with enumerated actions), but there is no "Use when..." clause or equivalent explicit trigger guidance; "for interactive CLIs" only weakly implies when. Per the guideline, a missing 'Use when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms include "tmux", "sessions", "panes", "capture output", "send keys", and "monitor prompts" — phrases a user would plausibly say. A few natural variations are missing (e.g. "terminal multiplexer", "attach", "scrollback"), so it fits anchor 4 rather than 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"tmux" names a clear niche with distinct triggers, and the enumerated pane-level operations make confusion with shell/terminal skills unlikely. It clearly matches anchor 5; anchor 4 would require some notable overlap with a closely related skill, which is not present.	5 / 5
	Total	16 / 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: OpenBMB/PilotDeck
Path: skills/tmux/SKILL.md
Commit: 66bfd09

Reviewed: 2 days 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.