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

Replace the entire description with a clear statement of what the skill does, listing specific concrete actions (e.g., 'Coordinates task distribution across multiple sub-agents, manages parallel workflows, and aggregates results').

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

Remove the invocation instruction ('invoke with $agent-v3-queen-coordinator') from the description field, as this is operational detail that doesn't help with skill selection.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for v3-queen-coordinator' is completely 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 impressive-sounding metrics but provides zero concrete instructions on what Claude should actually do when the skill is invoked. The content is entirely descriptive (topology diagrams, phase timelines, success metrics) with no executable guidance, commands, or decision-making workflows.

Suggestions

Add concrete, step-by-step instructions for what Claude should do when invoked as the Queen Coordinator (e.g., how to check agent status, assign tasks, create GitHub issues, resolve conflicts).

Include executable commands or code for core coordination operations like spawning agents, monitoring progress, and handling failures.

Add a workflow with validation checkpoints for the coordination process (e.g., verify agent readiness before dispatching tasks, check completion before advancing phases).

Replace the high-level phase descriptions with actionable decision trees or protocols Claude can follow to determine what action to take based on current project state.

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 Claude can execute. It explains concepts like what ADRs are and restates targets multiple times across frontmatter and body.	1 / 3
Actionability	There are no concrete commands, executable code, or specific step-by-step instructions for what Claude should actually do when this skill is invoked. The content describes a project structure and goals but never tells Claude how to coordinate agents, create issues, or perform any specific task.	1 / 3
Workflow Clarity	While phases are listed, there is no actionable workflow with clear steps Claude should follow. No validation checkpoints, no decision points, no error handling, and no concrete sequencing of operations. The phases describe what agents should do at a high level but not how the Queen Coordinator should orchestrate them.	1 / 3
Progressive Disclosure	The content has some structural organization with headers and sections, but there are no references to external files for detailed agent specifications, ADR details, or coordination protocols. Everything is inline but shallow - it's neither a useful overview pointing to details nor a complete reference.	2 / 3
	Total	5 / 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: f547cec

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