agent-manager-skill
Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
Install with Tessl CLI
npx tessl i github:duclm1x1/Dive-Ai --skill agent-manager-skill79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates specific capabilities around tmux-based agent management with good technical specificity. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords beyond technical jargon. The technical focus makes it distinctive but potentially harder for users to discover.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when managing background agents, running parallel CLI tasks, or scheduling automated agent workflows'
Include more natural language variations users might say: 'background processes', 'parallel agents', 'scheduled automation', 'terminal management'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'start/stop/monitor/assign' agents, manage 'tmux sessions', and 'cron-friendly scheduling'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (manage CLI agents via tmux with scheduling), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'tmux', 'CLI agents', 'cron', and 'sessions', but missing common variations users might say like 'background processes', 'terminal sessions', 'scheduled tasks', or 'agent management'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining tmux, CLI agents, and cron scheduling. The combination of these technologies creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides actionable commands for agent management. Its main strengths are token efficiency and executable examples. However, it lacks explicit workflow guidance for common multi-step scenarios (e.g., start agent -> verify running -> assign task -> monitor) and could better signal available documentation in the referenced repository.
Suggestions
Add a brief workflow example showing the typical sequence: start agent -> verify with list -> assign task -> monitor output
Include a validation step or expected output after 'start' command to confirm agent is running before assignment
Clarify what documentation exists in the repo (e.g., 'See agents/README.md for configuration options' or 'See docs/ for troubleshooting')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for all common operations (doctor, list, start, monitor, assign). The heredoc example for task assignment is particularly useful and executable. | 3 / 3 |
Workflow Clarity | Commands are listed but there's no explicit workflow sequence or validation checkpoints. For agent management involving multiple parallel processes, guidance on verifying agent state before/after operations would improve reliability. | 2 / 3 |
Progressive Disclosure | References the external repo for agent configuration examples but doesn't clearly signal what additional documentation exists there. The skill is appropriately concise but could better indicate where to find detailed configuration guides or troubleshooting. | 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.
- 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.