agent-queen-coordinator

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

2.93x

Quality

Does it follow best practices?

Impact

97%

2.93x

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-queen-coordinator/SKILL.md

Quality

Content

14%Scale 1-3

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

This skill is heavily over-themed with 'queen/hive/royal' metaphors that consume tokens without adding actionable value. While it provides some concrete MCP tool call examples for memory storage, the majority of the content is vague bullet lists, roleplay framing, and conceptual descriptions that Claude doesn't need. The skill lacks a clear workflow, validation steps, error handling, and any progressive disclosure structure.

Suggestions

Strip all thematic/roleplay language ('sovereign', 'royal decrees', 'coup prevention') and replace with direct, functional instructions for what the coordinator agent should actually do step-by-step.

Add a clear sequential workflow with validation checkpoints: e.g., 1. Check existing swarm state → 2. Identify unassigned tasks → 3. Allocate to agents → 4. Verify acknowledgment → 5. Monitor completion.

Convert vague bullet-list sections (Emergency Protocols, Governance Protocols, Succession Planning) into concrete executable steps or remove them entirely if they have no real implementation.

Ensure MCP tool call examples use the actual invocation syntax rather than JavaScript-style pseudocode, and add expected response handling for each call.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive roleplay framing ('sovereign intelligence', 'royal decrees', 'coup prevention'). Much of the content is thematic fluff that adds no actionable value. The skill explains concepts Claude doesn't need explained (what delegation is, what resource allocation means) and pads heavily with metaphorical language.	1 / 3
Actionability	The code blocks show concrete MCP tool calls with specific JSON structures, which is somewhat actionable. However, the code is JavaScript-style pseudocode rather than actual executable tool invocations, and many sections (Succession Planning, Governance Protocols, Emergency Protocols) are vague bullet lists with no concrete implementation.	2 / 3
Workflow Clarity	There is no clear sequenced workflow for the queen coordinator to follow. The content presents scattered responsibilities and code snippets without a coherent multi-step process. Command Protocols list 3 high-level patterns but lack validation checkpoints, error handling, or feedback loops for what are clearly complex orchestration operations.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no clear navigation structure. All content is inline with no separation of overview from detailed reference material. There are no bundle files to support progressive disclosure.	1 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when to use it, or what domain it operates in. It reads as a placeholder or auto-generated stub rather than a functional skill description.

Suggestions

Add concrete actions describing what queen-coordinator actually does (e.g., 'Coordinates parallel sub-agents to divide and execute complex multi-step tasks').

Add an explicit 'Use when...' clause with natural trigger terms that describe the situations where this skill should be selected.

Replace the internal name 'queen-coordinator' with descriptive language about the skill's domain and capabilities so Claude can match it to user requests.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for queen-coordinator' is entirely abstract with 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 it, not what it does or when to use it.	1 / 3
Trigger Term Quality	The only keyword is 'queen-coordinator', which is internal jargon and not a natural term any user would say. There are no natural language trigger terms.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no distinguishing characteristics. Without knowing what the skill does, it could conflict with anything or nothing.	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
Path: .agents/skills/agent-queen-coordinator/SKILL.md
Commit: 913f9ea

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.