tmux
Patterns for running long-lived processes in tmux. Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation.
88
83%
Does it follow best practices?
Impact
100%
1.14xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 is a solid description with clear 'when' guidance and good trigger terms that would help Claude select it appropriately. Its main weakness is the vague 'Patterns for' phrasing which doesn't specify concrete actions Claude would take (e.g., creating sessions, detaching, checking output). Overall it performs well for skill selection purposes.
Suggestions
Replace 'Patterns for running' with specific actions like 'Creates and manages tmux sessions for running long-lived processes' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (long-lived processes in tmux) and gives examples (dev servers, watchers, tilt), but doesn't list specific concrete actions like 'create tmux sessions', 'detach processes', or 'monitor output'. The word 'Patterns' is vague. | 2 / 3 |
Completeness | Clearly answers both what ('Patterns for running long-lived processes in tmux') and when ('Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'dev servers', 'watchers', 'tilt', 'tmux', 'long-lived processes', and 'outlive the conversation'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: tmux + long-lived processes is a very specific combination unlikely to conflict with other skills. The trigger terms (dev servers, watchers, tilt, outlive the conversation) clearly delineate this skill's scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, highly actionable skill with clear workflows, explicit validation steps, and well-defined constraints. Its main weakness is verbosity from repeated boilerplate (the SESSION variable derivation appears in nearly every code block) and overlapping patterns that could be consolidated. The content would benefit from a brief overview structure pointing to detailed examples rather than inlining everything.
Suggestions
Define the SESSION derivation once at the top and note that all subsequent snippets assume it, eliminating 10+ repetitions of the same line.
Consolidate overlapping patterns — 'Single Process', 'Adding a Window', and 'Start dev server if not running' share ~80% of their logic and could be unified into one idempotent template.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable examples, but there's significant repetition — the SESSION derivation line appears 12+ times across snippets, and several patterns overlap substantially (e.g., 'Starting Processes > Single Process' vs 'Common Patterns > Start dev server if not running'). Could be tightened by defining the session variable once and referencing it. | 2 / 3 |
Actionability | Every section provides fully executable bash commands with concrete examples. The code is copy-paste ready with real commands (npm run dev, tilt up, tail -f), proper tmux flags, and idempotent patterns. The WRONG vs CORRECT comparison is particularly actionable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints: check session exists → create if needed → add windows → send commands. The 'Wait for server ready' polling pattern and the monitoring/error-checking sections provide feedback loops. Isolation rules and the 'When to Use tmux' decision table add clear guardrails. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical progression from rules → basics → monitoring → lifecycle → common patterns. However, at ~180 lines it's a monolithic file that could benefit from splitting advanced patterns (monitoring, lifecycle, common patterns) into a separate reference file, keeping SKILL.md as a concise overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.