Name: agent-coordination
Rating: 78.60000000000001 (1 reviews)
Author: ruvnet

agent-coordination

Agent spawning, lifecycle management, and coordination patterns. Manages 60+ agent types with specialized capabilities. Use when: spawning agents, coordinating multi-agent tasks, managing agent pools. Skip when: single-agent work, no coordination needed.

1.34x

Quality

71%

Does it follow best practices?

Impact

89%

1.34x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-coordination/SKILL.md

The canonical home for this skill is agent-coordination in ruvnet/claude-flow

Quality

Content

58%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 body is concise and supplies executable commands and a useful routing table, but it lacks a sequenced coordination workflow with validation checkpoints and inlines a large agent catalog that would benefit from a reference file.

Suggestions

Add a short sequenced workflow for running a coordinated multi-agent task (e.g. route -> spawn pool -> assign -> verify -> stop) with an explicit validation/checkpoint step, which is currently missing for batch agent operations.

Move the 60+ agent type catalog into a references/ file (e.g. references/agent-types.md) and link to it from SKILL.md so the overview stays lean.

Include at least one concrete example showing agents being coordinated together (not just individual spawn/status commands) to close the actionability gap around actual coordination patterns.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; the only trim candidate is the long enumeration of 60+ agent types which could be condensed.	4 / 5
Actionability	Provides concrete, copy-paste-ready bash commands ('npx claude-flow agent spawn --type coder --name my-coder') covering common cases, with a minor gap in showing how to actually wire agents together for coordination.	4 / 5
Workflow Clarity	The Routing Codes table and Best Practices give only a rough mapping of task-to-agents with no sequenced coordination workflow and no validation/verification checkpoints for batch agent operations.	2 / 5
Progressive Disclosure	Sections are well-organized but no bundle files exist and the 60+ agent type catalog is inlined content that could reasonably live in a separate reference file; references are not signaled.	3 / 5
	Total	13 / 20 Passed

Description

83%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.

A strong, well-structured description that clearly states capabilities, gives explicit use/skip triggers, and stays concise. Trigger term coverage and distinctiveness are good but not exhaustive.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Agent spawning, lifecycle management, and coordination patterns', 'managing agent pools') rather than vague language, with only minor gaps in coverage of the full coordination surface.	4 / 5
Completeness	Explicitly answers both what ('Agent spawning, lifecycle management, and coordination patterns. Manages 60+ agent types') and when ('Use when: spawning agents, coordinating multi-agent tasks, managing agent pools'), plus a 'Skip when' boundary clause.	5 / 5
Trigger Term Quality	'Use when: spawning agents, coordinating multi-agent tasks, managing agent pools' gives good natural keyword coverage a user would actually say, though it lacks synonyms and broader variations.	4 / 5
Distinctiveness Conflict Risk	The multi-agent coordination niche is mostly distinct and the 'Skip when: single-agent work' clause reduces conflict risk, though it could still overlap with general orchestration/task-management skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/agent-coordination/SKILL.md
Commit: fa13ee4

Reviewed: about 4 hours 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.