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 somewhat limited coverage of natural user terms. Adding trigger guidance and more user-facing keywords would improve skill selection accuracy.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to interact with a running CLI program, control a tmux session, send keystrokes to a terminal, or read output from a tmux pane.'
Include additional natural trigger terms users might say, such as 'terminal multiplexer', 'send keys', 'capture terminal output', 'interact with running process', or 'automate CLI interaction'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'remote-control tmux sessions', 'sending keystrokes', 'scraping pane output', and specifies the context of 'interactive CLIs'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (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', 'capture output', 'tmux send-keys', or 'screen scraping'. A user might say 'interact with a running process' or 'control a terminal' which aren't covered. | 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 given 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 highly actionable tmux commands organized into clear categories. Its main weakness is the lack of validation/error-recovery patterns (e.g., checking if send-keys actually worked, handling missing sessions) and some mild verbosity in the use/don't-use sections. Overall it serves its purpose well as a quick reference for tmux session control.
Suggestions
Add a brief validation pattern after sending keys, e.g., capture-pane after send-keys to confirm the input was received and the expected prompt/output appeared.
Trim the 'When to Use' and 'When NOT to Use' sections to a single concise sentence or remove them — Claude can infer appropriate usage from the skill title and content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the 'When to Use' / 'When NOT to Use' checklists that are somewhat obvious, and the 'Notes' section restates things already demonstrated in examples. The example sessions table and session management section add moderate value but could be tighter. | 2 / 3 |
Actionability | Every section provides concrete, copy-paste-ready bash commands with specific flags and target syntax. The examples cover real scenarios (capturing output, sending keys, checking session status) with executable code throughout. | 3 / 3 |
Workflow Clarity | The 'Sending Input Safely' section shows a clear multi-step pattern with the sleep between sends, and the Claude Code patterns show practical sequences. However, there are no explicit validation checkpoints or error recovery steps — e.g., no guidance on what to do if capture-pane returns empty, or if send-keys doesn't produce expected results. | 2 / 3 |
Progressive Disclosure | For a standalone skill with no bundle files, the content is well-organized into logical sections with clear headers progressing from basic commands to advanced patterns. The structure is scannable and appropriately sized without needing external references. | 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.