tmux-processes
Patterns for running long-lived processes in tmux. Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation.
94
Quality
95%
Does it follow best practices?
Impact
90%
1.52xAverage 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 well-structured description with explicit 'Use when' guidance and good trigger terms that developers would naturally use. The main weakness is that it describes patterns rather than concrete actions - it could benefit from specifying what actions Claude will take (e.g., 'create tmux sessions', 'run commands in background').
Suggestions
Add specific actions like 'Creates tmux sessions, runs background processes, manages detached terminals' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (tmux, long-lived processes) and gives examples (dev servers, watchers, tilt), but doesn't describe concrete actions like 'create sessions', 'attach/detach', or 'manage windows'. | 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'dev servers', 'watchers', 'tilt', 'tmux', 'long-lived processes', and 'outlive the conversation' - these are terms developers naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on tmux and long-lived processes; the specific mention of 'outlive the conversation' and concrete examples like 'tilt' make it unlikely to conflict with general process or terminal skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that provides comprehensive, actionable guidance for tmux process management. It demonstrates best practices with clear anti-patterns (WRONG vs CORRECT), includes idempotent patterns with proper validation, and covers the full lifecycle from starting to monitoring to cleanup. The isolation rules section appropriately addresses safety concerns for multi-instance environments.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | All examples are fully executable bash commands that can be copy-pasted directly. The skill provides concrete patterns for every scenario including session creation, monitoring, lifecycle management, and common workflows. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation (checking if sessions/windows exist before creating). The idempotent patterns include proper conditionals and feedback, and the 'Wait for server ready' pattern shows a proper polling loop with timeout. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Starting, Monitoring, Lifecycle, Common Patterns) with a helpful decision table for when to use tmux. The skill is appropriately self-contained without needing external references for this scope. | 3 / 3 |
Total | 12 / 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
5342bca
- 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.