CtrlK
BlogDocsLog inGet started
Tessl Logo

tmux

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

77

2.00x
Quality

71%

Does it follow best practices?

Impact

86%

2.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is tmux in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 token-efficient, but workflow sequencing lacks validation checkpoints and the bundled helper scripts are not surfaced from the body.

Suggestions

Reference scripts/find-sessions.sh and scripts/wait-for-text.sh from the relevant sections so the bundled helpers are discoverable.

Add a validation checkpoint before destructive actions (e.g. capture-pane to confirm the target session before kill-session).

Frame the monitor → detect-prompt → approve flow as an explicit sequenced workflow with a verify step.

DimensionReasoningScore

Conciseness

The body is a lean command catalog with brief inline comments and no over-explanation of concepts Claude already knows; only minor items (the anecdotal session table) could be trimmed.

4 / 5

Actionability

Commands are fully executable and copy-paste ready, with specific examples covering the common cases (capture, send-keys, navigation, session management, safe input, Claude Code patterns).

5 / 5

Workflow Clarity

Loose sequences exist (check for prompts then approve, split text then Enter with sleep), but there are no explicit validation checkpoints, and the destructive kill-session path carries no verification guidance.

3 / 5

Progressive Disclosure

Section structure is clear, but the provided bundle scripts (scripts/find-sessions.sh, scripts/wait-for-text.sh) are never referenced or signaled in the body, leaving deeper material unnavigable.

3 / 5

Total

15

/

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 any explicit "when to use" guidance, which limits its completeness.

Suggestions

Append a "Use when..." clause naming concrete triggers, e.g. "Use when monitoring or driving interactive CLIs running in tmux panes."

Add common synonyms or phrasings users might say (e.g. "drive a tmux session", "read tmux output") to broaden trigger coverage.

DimensionReasoningScore

Specificity

"sending keystrokes and scraping pane output" names several concrete actions on a clearly identified domain (tmux sessions, interactive CLIs), with only minor coverage gaps.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural terms like "tmux sessions", "interactive CLIs", "keystrokes", and "pane output" give good keyword coverage a user would actually say, missing only a few synonyms.

4 / 5

Distinctiveness Conflict Risk

The tmux-specific niche with distinct triggers (keystrokes, pane output, interactive CLIs) makes conflict with other skills minimal.

5 / 5

Total

16

/

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.

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
trpc-group/trpc-agent-go
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.