agent-manager-skill
Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
67
60%
Does it follow best practices?
Impact
Pending
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 identifying the domain of managing CLI agents via tmux with cron scheduling. Its main weakness is the absence of an explicit 'Use when...' clause, which limits completeness. The trigger terms are somewhat technical and could benefit from more natural user-facing language.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to orchestrate multiple CLI agents, manage tmux sessions, or schedule agent tasks with cron.'
Include more natural trigger terms users might say, such as 'background agents', 'parallel tasks', 'agent orchestration', or 'session management'.
| 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' (manage local CLI agents via tmux with start/stop/monitor/assign and cron scheduling), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'tmux', 'CLI agents', 'cron', 'scheduling', but misses common user variations like 'background tasks', 'parallel agents', 'agent orchestration', or 'session management'. The terms are somewhat technical and may not match how users naturally phrase requests. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining tmux sessions, local CLI agents, and cron scheduling. Very unlikely to conflict with other skills due to the specific combination of tmux + agent management + cron. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is commendably concise and provides real CLI commands, but it reads more like a quick reference card than a complete skill. It lacks workflow sequencing (e.g., run doctor first, then configure agents, then start), validation/error handling guidance, and concrete details about agent configuration. For a multi-agent management skill involving parallel processes, the absence of monitoring/recovery workflows is a significant gap.
Suggestions
Add an explicit workflow sequence: e.g., 1. Run `doctor` to verify prerequisites, 2. Configure agents in `agents/`, 3. Start agents, 4. Verify with `list`, 5. Monitor — with validation checkpoints after each step.
Include expected output examples for key commands (especially `doctor` and `list`) so Claude knows what success vs failure looks like.
Replace 'see the repo for examples' with a direct link to a specific configuration file or include a minimal agent config example inline.
Add error recovery guidance: what to do if an agent fails to start, how to check logs for errors, how to clean up stale tmux sessions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what tmux is or how CLI agents work. Every section earns its place. | 3 / 3 |
Actionability | Provides concrete CLI commands that are copy-paste ready, but lacks detail on agent configuration (the agents/ directory structure), expected outputs, and what 'doctor' checks. The 'see the repo for examples' is vague. | 2 / 3 |
Workflow Clarity | Commands are listed but there's no clear workflow sequence, no validation checkpoints, and no error recovery guidance. For managing multiple agents (a potentially destructive/complex operation), there's no feedback loop for verifying agent status after start, no guidance on what to do if start fails, and no sequencing of doctor → start → monitor. | 1 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but the reference to 'see the repo for examples' is vague and not a well-signaled pointer. No links to specific configuration docs or example files within the repo. | 2 / 3 |
Total | 8 / 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
d739c8b
- 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.