tmux

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

Quality

73%

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

76%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 content is highly actionable and well-structured with real referenced scripts, but destructive and batch operations lack explicit validation checkpoints, capping workflow clarity, and the advanced multi-agent example inflates the body where a reference file would be cleaner.

Suggestions

Add a validation checkpoint before destructive cleanup (e.g. confirm sessions via list-sessions before kill-session/kill-server, and verify target name to avoid killing the wrong session).

Move the multi-session codex-army orchestration example into a separate reference file (e.g. references/parallel-agents.md) and link to it, tightening the main body.

For the parallel-agent polling loop, add an explicit completion-verification step (capture and assert prompt returned) rather than only a grep check, to give the batch workflow a proper feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding about what tmux is; it earns 4 rather than 5 because the multi-session codex-army example is sizable and could be trimmed or moved to a reference.	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands covering the common cases (start session, send input safely, capture output, wait for text, cleanup), plus concrete helper-script usage with documented flags.	5 / 5
Workflow Clarity	The quickstart sequences start-session then print-monitor-commands and the wait-for-text helper gives a feedback loop, but destructive operations (kill-session/kill-server) and the batch parallel-agent orchestration lack validation checkpoints, which caps workflow_clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is organized into clearly headed sections with one-level-deep, clearly signaled references to real bundle scripts ({baseDir}/scripts/find-sessions.sh and wait-for-text.sh); earns 4 not 5 because the large inline advanced example could be split into a reference file.	4 / 5
	Total	16 / 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.

The description is specific, distinctive, and uses natural trigger terms, but it omits an explicit "Use when..." usage clause, capping its completeness at 3. Adding a trigger phrase such as "Use when you need an interactive TTY for a CLI that exec/background mode cannot drive" would lift it.

Suggestions

Add an explicit "Use when..." clause naming the trigger situations, e.g. "Use when you need an interactive TTY for a CLI that cannot run via exec/background mode."

Include a few more natural synonyms ("terminal", "TTY", "send-keys") to broaden trigger term coverage.

Optionally mention attaching/monitoring or spawning sessions to round out the concrete-action list toward a 5 on specificity.

Dimension	Reasoning	Score
Specificity	"sending keystrokes and scraping pane output" names the tmux/interactive-CLI domain plus several concrete actions, with only minor coverage gaps; not a 5 because it omits further actions like attaching or spawning sessions.	4 / 5
Completeness	The description clearly states what the skill does, but there is no explicit "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ("tmux", "interactive CLIs", "sending keystrokes", "scraping pane output"), but common synonyms like "terminal", "TTY", or "send-keys" are missing, so it is not comprehensive enough for a 5.	4 / 5
Distinctiveness Conflict Risk	"Remote-control tmux sessions for interactive CLIs" carves out a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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: dbf3fcc

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.