CtrlK
BlogDocsLog inGet started
Tessl Logo

tmux

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

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The skill body is a high-quality, lean command reference with executable examples, clear sequences, a polling/validation helper, and well-organized one-level-deep references to real bundle scripts.

DimensionReasoningScore

Conciseness

The body is lean: it assumes Claude knows tmux and presents mostly executable commands and short bullets with no padding or concept explanations, so nearly every token earns its place.

3 / 3

Actionability

It provides copy-paste-ready bash for socket setup, session creation, send-keys, and capture-pane, plus fully documented helper-script invocations with flags, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sequences are clear (Quickstart, the parallel-agent orchestration with a completion poll loop) and the wait-for-text helper supplies an explicit wait/validate mechanism; for this reference-style skill the organization is clear and well-sequenced.

3 / 3

Progressive Disclosure

Content is split into well-signaled sections with one-level-deep references to real helper scripts ({baseDir}/scripts/find-sessions.sh and wait-for-text.sh, both present), keeping the overview concise and navigation easy.

3 / 3

Total

12

/

12

Passed

Description

67%

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 and distinctive about tmux session control, but it omits an explicit usage-trigger clause and relies on somewhat technical phrasing rather than the natural terms a user would say.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you need an interactive TTY or to drive a terminal/CLI program that exec background mode cannot handle.'

Include more natural user-facing trigger terms such as 'terminal', 'TTY', or 'interactive program' alongside 'tmux' and 'interactive CLIs'.

DimensionReasoningScore

Specificity

The phrase 'Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output' lists multiple concrete actions (remote-control, sending keystrokes, scraping pane output), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does, but lacks an explicit 'Use when...' trigger clause answering when Claude should use it; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

'tmux sessions' and 'interactive CLIs' are relevant natural terms, but the description leans on technical jargon ('scraping pane output', 'sending keystrokes') and omits common variations users would say like 'terminal', 'TTY', or 'run an interactive program'.

2 / 3

Distinctiveness Conflict Risk

The tmux/interactive-CLI niche is clearly specific with distinct triggers and is very unlikely to overlap with or trigger for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation14 / 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
volcengine/OpenViking
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.