agent-v3-queen-coordinator

Agent skill for v3-queen-coordinator - invoke with $agent-v3-queen-coordinator

6.25x

Quality

Does it follow best practices?

Impact

100%

6.25x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-v3-queen-coordinator/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is essentially a placeholder that provides no useful information about the skill's capabilities, domain, or appropriate usage context. It fails on every dimension because it only contains an invocation instruction and an opaque internal name, making it impossible for Claude to determine when to select this skill over others.

Suggestions

Add a clear statement of what the skill does with specific concrete actions (e.g., 'Coordinates task distribution across multiple sub-agents for parallel processing' or whatever the actual functionality is).

Add an explicit 'Use when...' clause with natural trigger terms that describe the situations or user requests that should activate this skill.

Replace the internal project name with descriptive language about the skill's domain and purpose so it can be distinguished from other skills in a large skill library.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for v3-queen-coordinator' is entirely abstract and gives no indication of what the skill actually does.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states how to invoke the agent, not what it does or when it should be selected.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say. 'v3-queen-coordinator' is internal jargon/a project name, and 'invoke with $agent-v3-queen-coordinator' is a technical invocation instruction, not a trigger term.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no basis for distinguishing this skill from any other. The only distinguishing element is the opaque name 'v3-queen-coordinator', which conveys no semantic meaning about its purpose.	1 / 3
	Total	4 / 12 Passed

Implementation

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

This skill reads as a project planning document rather than an actionable skill for Claude. It describes an ambitious 15-agent coordination system with topology diagrams and timeline phases but provides zero concrete instructions on how to actually perform coordination, dispatch tasks, manage agent communication, or handle failures. The content would need a complete rewrite to be useful as a skill.

Suggestions

Replace the project overview with concrete, executable coordination workflows: how to spawn agents, assign tasks, check status, and handle failures with specific commands or tool invocations.

Add validation checkpoints and feedback loops for coordination operations (e.g., how to verify an agent completed its task, how to handle blocked dependencies, how to retry failed operations).

Move the topology diagram and phase timeline to a separate PLAN.md or ARCHITECTURE.md file, and use the SKILL.md body for actionable step-by-step orchestration instructions.

Include concrete examples of coordination actions: e.g., creating GitHub issues for agents, checking agent progress, resolving cross-agent dependencies with specific commands.

Dimension	Reasoning	Score
Conciseness	The content is heavily padded with organizational/planning information (agent topology diagrams, phase timelines, success metrics) that describe project management rather than providing actionable instructions. It explains concepts and structures without giving Claude concrete guidance on what to actually do.	1 / 3
Actionability	There are no concrete commands, executable code, or specific step-by-step instructions for Claude to follow. The content describes a project structure and goals but never tells Claude what actions to take, what tools to use, or how to coordinate agents in practice.	1 / 3
Workflow Clarity	While phases are listed, there are no actual workflow steps, no validation checkpoints, no error recovery, and no concrete sequencing of operations. The phases describe what agents should work on at a high level but not how to orchestrate them.	1 / 3
Progressive Disclosure	The content is a monolithic block with no references to external files for detailed agent configurations, ADR specifications, or coordination protocols. All the high-level information is inline with no pointers to where the actual implementation details live.	1 / 3
	Total	4 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Commit: 0d9f9b1

Reviewed: 3 days 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.