tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 effectively communicates specific technical capabilities for tmux automation with good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords beyond technical jargon.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when automating terminal sessions, controlling interactive CLI programs, or when the user needs to interact with tmux panes'
Include more natural keyword variations such as 'terminal automation', 'command line control', 'shell session', or 'terminal multiplexer' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'remote-control tmux sessions', 'sending keystrokes', and 'scraping pane output'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (remote-control tmux sessions, send keystrokes, scrape output) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'tmux', 'keystrokes', 'pane output', and 'interactive CLIs', but misses common user variations like 'terminal automation', 'command line', 'shell session', or 'terminal multiplexer'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focusing specifically on tmux session control. The combination of 'tmux', 'keystrokes', and 'pane output' creates a clear, unique domain unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that efficiently teaches tmux session control with concrete, executable examples. The 'When to Use' and 'When NOT to Use' sections provide excellent scoping. The main weakness is the lack of explicit validation/feedback loops when sending input to sessions, which could lead to issues in automated workflows.
Suggestions
Add a validation step after sending keys, e.g., 'After sending input, capture output to verify the command was received: tmux capture-pane -t shared -p | tail -3'
Include a feedback loop pattern for the 'Approve Claude Code Prompt' section showing how to verify the approval was processed before moving on
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only essential commands and patterns without explaining what tmux is or how terminals work. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | All examples are fully executable bash commands that can be copy-pasted directly. The skill provides specific session names, exact command syntax, and real-world patterns like checking for prompts with grep. | 3 / 3 |
Workflow Clarity | While individual commands are clear, the skill lacks explicit validation steps for multi-step operations. For example, after sending keys to a session, there's no guidance on verifying the input was received or checking for errors before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections progressing from basic commands to advanced patterns. At ~100 lines, it appropriately keeps everything in one file with logical groupings and a helpful table for session examples. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.