CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-manager-skill

Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

48

Quality

52%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/agent-manager-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 reasonable starting point with concrete CLI commands, but falls short on workflow clarity—there's no sequenced process, no validation checkpoints, and no error handling guidance for managing multiple agents. The content is moderately concise but includes generic boilerplate limitations, and key details about agent configuration and expected outputs are missing.

Suggestions

Add a sequenced workflow (e.g., 1. Run 'doctor' to verify prerequisites, 2. Check output for errors, 3. Start agent, 4. Verify with 'list' or 'monitor', 5. Assign task) with explicit validation checkpoints between steps.

Include example output for key commands (especially 'doctor' and 'list') so Claude knows what success and failure look like.

Replace the generic 'Limitations' boilerplate with skill-specific constraints (e.g., max concurrent agents, what happens if tmux isn't installed, how to recover a crashed agent).

Provide concrete details about the agents/ directory structure and configuration format, or reference a specific file path in the bundle rather than vaguely saying 'see the repo'.

DimensionReasoningScore

Conciseness

Mostly efficient, but the 'Limitations' section contains generic boilerplate advice (e.g., 'stop and ask for clarification') that doesn't add value for Claude. The 'When to Use' section is slightly redundant with the commands shown.

2 / 3

Actionability

Provides concrete CLI commands which is good, but lacks key details: no explanation of what 'doctor' does, no example output, no guidance on agent configuration (agents/ directory structure), and the heredoc example doesn't explain the task format. The git clone URL points to an external repo with no verification that it exists or works.

2 / 3

Workflow Clarity

Commands are listed but there's no sequenced workflow—no indication of what order to run things, no validation steps (e.g., check 'doctor' output before proceeding, verify agent started successfully), and no error recovery guidance. For managing multiple agents (a potentially destructive/complex operation), this is insufficient.

1 / 3

Progressive Disclosure

The skill references an external repo ('see the repo for examples') but provides no bundle files and no specific file references. The content is reasonably short and organized with clear sections, but the vague external reference without concrete paths or filenames weakens navigation.

2 / 3

Total

7

/

12

Passed

Description

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 would help Claude know exactly when to select this skill. The trigger terms are decent but could benefit from more natural user-facing language variations.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to run multiple agents in parallel, orchestrate background CLI tasks, or schedule agent work via cron.'

Include additional natural trigger terms users might say, such as 'parallel agents', 'background tasks', 'agent orchestration', 'run multiple agents simultaneously'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'start/stop/monitor/assign' agents, manage via tmux sessions, and includes 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 specifying when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant keywords like 'tmux', 'CLI agents', 'cron', 'scheduling', 'start/stop/monitor'. However, it misses common user variations like 'background tasks', 'parallel agents', 'agent orchestration', or 'run multiple agents'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: the combination of tmux sessions, local CLI agents, and cron scheduling is very specific and unlikely to conflict with other skills.

3 / 3

Total

10

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
sickn33/antigravity-awesome-skills
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.