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.

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/agent-manager-skill/SKILL.md

The canonical home for this skill is agent-manager-skill in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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 executable commands, but it lacks workflow sequencing, validation steps, and sufficient detail about agent configuration and expected outputs. It reads more like a quick reference card than a complete skill that would guide Claude through managing agents end-to-end.

Suggestions

Add a numbered workflow showing the typical sequence: run doctor to verify prerequisites, configure agents, start them, monitor, and handle failures — with explicit validation checkpoints (e.g., 'verify doctor output shows all green before proceeding').

Include expected output examples for key commands (e.g., what 'list' and 'doctor' return) so Claude can verify correct operation.

Replace 'see the repo for examples' with specific file references (e.g., 'See agents/example-agent.yaml for configuration format') or include a minimal agent configuration example inline.

Add a brief section on cron scheduling with a concrete crontab entry example, since it's mentioned in the skill description but absent from the content.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what tmux is, what CLI agents are, or how cron works. Every section serves a purpose and no token is wasted on concepts Claude already knows.

3 / 3

Actionability

The common commands section provides concrete, executable CLI commands with examples including a heredoc for task assignment. However, key details are missing: there's no explanation of what 'EMP_0001' refers to, how to configure agents, what the 'doctor' command checks, or what output to expect. The 'see the repo for examples' is vague.

2 / 3

Workflow Clarity

The commands are listed without any sequencing or workflow context. There's no guidance on the order of operations (e.g., run doctor first, then configure agents, then start), no validation checkpoints, and no error handling or feedback loops for when agents fail or commands produce unexpected output.

1 / 3

Progressive Disclosure

The content is appropriately brief for a SKILL.md overview, but references to supporting materials are vague ('see the repo for examples') rather than pointing to specific files. No bundle files are provided, so there's no clear navigation structure to deeper documentation about agent configuration, cron setup, or troubleshooting.

2 / 3

Total

8

/

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
Dokhacgiakhoa/antigravity-ide
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.