agent-manager-skill
Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
48
52%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agent-manager-skill/SKILL.mdQuality
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 is concise and specific about its capabilities, clearly naming the technologies involved (tmux, cron, CLI agents) and the actions supported (start/stop/monitor/assign). Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are somewhat technical and could benefit from more natural-language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to orchestrate, schedule, or manage multiple CLI agents running in parallel.'
Include more natural trigger terms users might say, such as 'run multiple agents', 'background agents', 'parallel tasks', or 'agent orchestration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'start/stop/monitor/assign' agents via tmux sessions, with 'cron-friendly scheduling'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (manage local CLI agents via tmux with scheduling), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'tmux', 'CLI agents', 'cron', 'scheduling', 'sessions', but misses common user variations like 'background tasks', 'parallel agents', 'agent orchestration', or 'run multiple agents'. Some terms are fairly technical. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of tmux sessions, local CLI agents, and cron scheduling creates a very distinct niche. Unlikely to conflict with other skills due to the specific technology stack mentioned. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a basic command reference for the agent-manager tool but lacks the depth needed for reliable use. The commands are concrete but presented as an unsequenced list without workflow guidance, validation steps, or error handling. Key information like agent configuration format, expected outputs, and troubleshooting steps are missing or deferred to an external repo without specific references.
Suggestions
Add a clear numbered workflow showing the typical sequence: run doctor → configure agents → start → monitor → assign tasks, with validation checkpoints (e.g., check 'list' output after starting an agent).
Include example output for key commands (especially 'doctor', 'list', and 'monitor') so Claude knows what success and failure look like.
Document the agent configuration format (what goes in agents/ directory, required fields) or provide a concrete reference to a specific file in the repo rather than a vague 'see the repo'.
Remove the generic 'Limitations' boilerplate and replace with tool-specific constraints (e.g., max concurrent agents, tmux session naming conventions, what happens on agent crash).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections. The 'Limitations' section contains generic boilerplate advice (e.g., 'Do not treat the output as a substitute for environment-specific validation') that doesn't add value for Claude. The 'When to Use' section is reasonable but slightly redundant with the commands shown. | 2 / 3 |
Actionability | The common commands section provides concrete, copy-paste-ready CLI commands which is good. However, there's no explanation of what the commands return, no example output, and the agent configuration (agents/ directory structure, config format) is left entirely unexplained, making it incomplete for actually setting up and using the tool. | 2 / 3 |
Workflow Clarity | There is no clear workflow sequence for multi-step processes. The commands are listed but not sequenced into a coherent workflow (e.g., when to use 'doctor' vs 'start' vs 'monitor'). There are no validation checkpoints, no error handling guidance, and no feedback loops for monitoring agent status or handling failures. | 1 / 3 |
Progressive Disclosure | The skill references a repo ('see the repo for examples') but doesn't provide clear, well-signaled links to specific files. No bundle files are provided, so there's no supporting documentation for agent configuration, advanced usage, or troubleshooting. The structure is flat but reasonably organized for its size. | 2 / 3 |
Total | 7 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
45bad85
- 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.