agent-manager-skill

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/agent-manager-skill/SKILL.md

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

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is commendably concise and gives concrete executable commands, but it does not sequence multi-step agent workflows with validation checkpoints and leans on external/unbundled references without clear navigation. Adding an explicit ordered workflow with verify steps would lift the two lower dimensions.

Suggestions

Add a short ordered workflow (e.g. doctor -> start -> monitor --follow -> assign) with an explicit validation/check step after start or assign, given the batch/automated nature of the operations.

Make external/unbundled references explicit and one-level-deep, e.g. note which paths live in the cloned repo vs. locally, and link concrete files rather than 'see the repo'.

Include a one-line verification that a session started (e.g. check `list` output) to satisfy the validation-checkpoint expectation for batch operations.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — when-to-use bullets, prerequisites, a few concrete commands, and terse notes with no padding or over-explanation of concepts Claude already knows.	5 / 5
Actionability	Provides concrete, executable commands (python3 agent-manager/scripts/main.py ...), but execution depends on cloning an external repo and references a teams/*.md workflow not bundled here, leaving minor gaps.	4 / 5
Workflow Clarity	Commands are listed but not sequenced as a workflow with validation checkpoints; because start/stop/assign and cron scheduling are batch/automated operations, missing validation caps this at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no bundle files to over-split, but it points to an external repo and unbundled local paths (agents/, teams/*.md) rather than clearly-signaled one-level-deep local references, leaving a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 clearly states what the skill does and lists concrete actions in a distinct niche, but it omits an explicit trigger ('Use when...') and relies on somewhat limited natural-language keyword variations. Adding a 'Use when' clause would materially raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when you need to run, monitor, or schedule several local CLI agents at once.'

Add natural synonyms users actually say, such as 'background agents', 'parallel agents', 'agent sessions', or 'scheduled agent tasks'.

Tighten the action list toward comprehensive coverage (e.g. include 'tail logs' and 'assign tasks') to push specificity to 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('multiple local CLI agents via tmux sessions') and several concrete actions ('start/stop/monitor/assign', 'cron-friendly scheduling'), but coverage is not comprehensive enough for a 5.	4 / 5
Completeness	Provides a clear 'what' but no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes some relevant keywords ('CLI agents', 'tmux sessions', 'cron', 'scheduling') but lacks common natural variations or synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	'Manage multiple local CLI agents via tmux sessions' defines a clear niche with minimal overlap risk; falls just short of the fully-distinct anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/agent-manager-skill/SKILL.md
Commit: 900c504

Reviewed: 15 minutes ago

Table of Contents

Discovery Implementation Validation

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.