tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
76
70%
Does it follow best practices?
Impact
86%
2.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/tmux/SKILL.mdQuality
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 is concise and technically specific, clearly identifying the skill's niche of tmux session control. Its main weaknesses are the lack of an explicit 'Use when...' trigger clause and missing some natural user-facing keyword variations. The distinctiveness is excellent, making it easy to differentiate from other skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with tmux sessions, automate terminal commands, or work with interactive CLI tools that require keystroke input.'
Include additional trigger term variations such as 'terminal multiplexer', 'send-keys', 'capture-pane', 'automate terminal', or 'screen scraping' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'remote-control tmux sessions', 'sending keystrokes', and 'scraping pane output'. These are specific, actionable capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers 'what' (remote-control tmux sessions by sending keystrokes and scraping pane output), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'tmux', 'keystrokes', 'pane output', and 'interactive CLIs', but misses common user variations like 'terminal multiplexer', 'send keys', 'tmux send-keys', 'capture-pane', or 'screen scraping'. Users might also say 'automate terminal' or 'control terminal session'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — tmux session control via keystrokes and pane scraping is a very specific niche. Unlikely to conflict with other skills due to the precise domain of tmux remote control for interactive CLIs. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, practical skill that provides concrete, executable tmux commands organized in a logical progression. Its main weakness is the lack of explicit validation steps in workflows (e.g., verifying that sent keys were received or that a session is in the expected state before sending input). The 'When to Use / When NOT to Use' sections add some bulk without proportional value.
Suggestions
Add a validation step after sending keys, e.g., 'After sending input, capture-pane and verify the expected response appeared before proceeding.'
Remove or condense the 'When to Use' and 'When NOT to Use' sections—the skill title and description already convey scope, and Claude can infer appropriate usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the 'When NOT to Use' list and the 'Notes' section with things Claude already knows (e.g., 'Sessions persist across SSH disconnects'). The 'When to Use' section is also somewhat redundant given the clear title and description. However, the command examples themselves are lean. | 2 / 3 |
Actionability | All commands are concrete, executable, and copy-paste ready. The examples cover real scenarios (capturing output, sending keys, checking session status) with specific flags and target syntax. The loop for checking all sessions and the safe input pattern with sleep are particularly actionable. | 3 / 3 |
Workflow Clarity | The skill presents clear individual commands but lacks explicit multi-step workflows with validation checkpoints. The 'Sending Input Safely' section hints at a sequence but doesn't include verification (e.g., confirming the input was received). The Claude Code patterns are useful but presented as isolated commands rather than a validated workflow. | 2 / 3 |
Progressive Disclosure | For a skill of this scope (single-purpose, under 100 lines, no bundle files), the content is well-organized with clear section headers that progress from basic (list sessions, capture output) to advanced (Claude Code session patterns). No external references are needed and the structure supports easy scanning. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- attilaczudor/Test
- Commit
b4fc4af
- 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.