tmux

Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.

Quality

75%

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

Fix and improve this skill with Tessl

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

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.

The body is an exemplary lean skill: executable commands throughout, a complete quickstart, real and clearly-signaled helper scripts, and well-organized sections. The only minor gap is the absence of an explicit post-launch verification step (e.g. confirm the REPL prompt appeared before sending commands).

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative throughout ('Prefer literal sends: tmux -S "$SOCKET" send-keys -t target -l -- "$cmd"'), explains nothing Claude already knows, and every section earns its tokens — matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	The quickstart is a complete copy-paste-ready block (create socket dir, new session, send keys, capture pane) and the helper scripts are documented with exact invocations and all flags ('-T timeout seconds (integer, default 15)'), covering the common cases fully.	5 / 5
Workflow Clarity	Sequences are clear (quickstart start→send→capture, then 'always print monitor commands', plus a poll-for-completion loop with wait-for-text.sh as a feedback mechanism), but there is no explicit checkpoint verifying that a session or REPL actually started before sending input — a minor validation gap that keeps it below the level-5 anchor.	4 / 5
Progressive Disclosure	The two bundle scripts (find-sessions.sh, wait-for-text.sh) both exist and are referenced one level deep with clear `{baseDir}/scripts/...` paths and a dedicated helper section, while the body stays a well-organized overview — matching the 'clear overview with well-signaled one-level-deep references' anchor.	5 / 5
	Total	19 / 20 Passed

Description

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

The description is concrete and highly distinctive thanks to the specific tool name, but it omits any 'when to use' trigger guidance and lacks natural keyword variations like terminal, TTY, or REPL. Adding an explicit 'Use when...' clause would lift both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you need to drive an interactive terminal, REPL, or CLI (Python, node, shells) in a persistent TTY session.'

Include natural synonyms such as 'terminal', 'TTY', 'REPL', and 'shell session' so users' phrasing matches the description.

Mention one or two more concrete capabilities (e.g. attach/detach, kill sessions, run parallel agents) to round out the action list.

Dimension	Reasoning	Score
Specificity	The description names the domain ('tmux sessions for interactive CLIs') and two concrete actions ('sending keystrokes and scraping pane output'), matching the '1-2 concrete actions but not comprehensive' anchor; it is not level 4 because it does not list several specific actions like attach, kill, or parallel orchestration.	3 / 5
Completeness	It has a clear 'what' (remote-control tmux via keystrokes and pane scraping) but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; it is not level 2 because the 'what' is concrete and specific.	3 / 5
Trigger Term Quality	'tmux', 'sessions', 'interactive CLIs', and 'keystrokes' are relevant keywords, but common variations users would naturally say — 'terminal', 'TTY', 'REPL', 'shell session' — are missing, matching the 'some relevant keywords but missing common variations' anchor rather than the good-coverage level 4.	3 / 5
Distinctiveness Conflict Risk	'tmux' names a specific tool with a clear niche, and the interactive-CLI framing is distinct, so it is unlikely to trigger for the wrong skill — matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: volcengine/OpenViking
Path: bot/workspace/skills/tmux/SKILL.md
Commit: b2f1f9d

Reviewed: 3 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.