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:sickn33/antigravity-awesome-skills --skill agent-manager-skill71
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/skillAgent success when using this skill
Validation 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.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to run multiple agents in parallel, manage background CLI processes, or schedule agent tasks'
Include more natural language variations users might say, such as 'background agents', 'parallel processes', 'scheduled automation', or 'agent orchestration'
| 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 user variations like 'background processes', 'terminal sessions', 'scheduled tasks', or 'agent orchestration'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining tmux, CLI agents, and cron scheduling. Unlikely to conflict with other skills due to the specific technical domain. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise and provides executable commands, which are strengths. However, it lacks workflow sequencing (when to use doctor vs list vs start), validation checkpoints, and clearer references to detailed documentation. The skill would benefit from a brief workflow showing the typical sequence of operations.
Suggestions
Add a brief workflow section showing the typical sequence: doctor → list → start → monitor/assign, with validation checkpoints
Clarify what 'doctor' checks and what to do if it reports issues
Replace 'see the repo for examples' with specific file references like 'See [agents/README.md](agent-manager/agents/README.md) for configuration format'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose and the token budget is well-respected. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands which is good, but lacks context on what each command does beyond the command name, and the heredoc example for 'assign' assumes knowledge of the teams file structure without explanation. | 2 / 3 |
Workflow Clarity | Commands are listed but there's no clear workflow sequence showing how to go from setup to running agents. Missing validation steps (e.g., what does 'doctor' check for, what to do if it fails) and no error recovery guidance. | 2 / 3 |
Progressive Disclosure | References the external repo for examples and agent configuration, but the signaling is vague ('see the repo for examples'). Could benefit from clearer pointers to specific documentation files within the cloned repo. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.