tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
80
Quality
77%
Does it follow best practices?
Impact
80%
1.37xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/tmux/SKILL.mdDiscovery
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.
This 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 the technical terminology.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when automating interactive CLI programs, controlling terminal sessions, or when the user needs to interact with programs that require keyboard input'
Include additional natural trigger terms users might say: 'terminal automation', 'interactive programs', 'send keys', 'automate CLI', 'terminal control'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'remote-control tmux sessions', 'sending keystrokes', and 'scraping pane output'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly describes what it does (remote-control tmux, send keystrokes, scrape output) but lacks an explicit 'Use when...' clause to guide Claude on when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes good technical terms like 'tmux', 'keystrokes', 'pane output', but missing common user phrases like 'terminal automation', 'interactive programs', 'CLI tools', or 'send keys'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - tmux session control is specific and unlikely to conflict with other skills. The combination of 'tmux', 'keystrokes', and 'pane output' creates a clear, unique domain. | 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, well-crafted skill that provides concrete, executable guidance for tmux session management. The content is appropriately concise and assumes Claude's competence with shell scripting. The main weakness is the lack of explicit error handling and validation steps in multi-step workflows, particularly in the orchestration section.
Suggestions
Add explicit error handling to the orchestration workflow (e.g., what to do if an agent fails or hangs)
Include a validation checkpoint after spawning sessions to confirm they started correctly before sending commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only project-specific conventions (socket paths, naming, helper scripts) without explaining what tmux is or how it works. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | All examples are fully executable bash commands that can be copy-pasted directly. The quickstart, orchestration example, and helper script usage all provide complete, working code with specific flags and arguments. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the orchestration workflow lacks explicit validation checkpoints. The polling example checks for completion but doesn't provide a feedback loop for handling failures or retrying. Cleanup is documented but not integrated into workflows. | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (quickstart, conventions, orchestration, cleanup, helper). References to external scripts are one-level deep and clearly signaled with paths. The skill is appropriately self-contained for its scope. | 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.