tmux
Patterns for running long-lived processes in tmux. Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation.
96
Quality
95%
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 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, making it slightly vague about what specific capabilities the skill provides (e.g., session management, output monitoring).
Suggestions
Add specific actions the skill enables, such as 'create tmux sessions, monitor output, manage background processes' 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'. 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 file that provides comprehensive, actionable guidance for tmux process management. It establishes clear hard requirements upfront, provides executable code for every pattern, and includes helpful decision tables and common patterns. The content is appropriately scoped and well-organized without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with bash and tmux. Every section provides actionable patterns without explaining what tmux is or how bash works. | 3 / 3 |
Actionability | All code examples are fully executable bash scripts with proper variable handling. The WRONG/CORRECT comparison and copy-paste ready patterns make implementation unambiguous. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation (checking session exists, checking window exists). The idempotent patterns include proper conditionals and feedback messages. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers progressing from rules to patterns to common use cases. The decision table for 'When to Use tmux' provides excellent quick reference. No external references needed for this self-contained skill. | 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.