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 known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-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 purpose, capabilities, or when it should be used. It only contains an invocation command, which is insufficient for Claude to make any informed selection decision among multiple skills.

Suggestions

Add a clear statement of what the skill does with specific concrete actions (e.g., 'Coordinates parallel sub-agents to divide and execute complex multi-step tasks').

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

Replace the internal name 'queen-coordinator' with a meaningful description of the domain or workflow this skill addresses to improve distinctiveness.

Dimension	Reasoning	Score
Specificity	The description contains 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 the invocation command without explaining purpose or trigger conditions.	1 / 3
Trigger Term Quality	No natural keywords a user would say are present. 'queen-coordinator' is internal jargon, and 'invoke with $agent-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 distinguishing characteristics. Without knowing what the skill does, it could conflict with anything or nothing — Claude has no basis for selection.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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' metaphorical language that obscures the actual coordination logic. While it provides some concrete MCP memory store examples, most sections are abstract bullet lists or static JSON payloads with placeholder values. The skill lacks real workflow sequencing, validation steps, error recovery, and any progressive disclosure structure.

Suggestions

Strip the roleplay/metaphorical language (sovereign, royal decrees, coup prevention, morale) and replace with direct technical instructions for coordination tasks

Add concrete multi-step workflows with validation: e.g., 'Store directive → Query agent status → Verify acknowledgment → Handle timeout/failure'

Replace hardcoded placeholder JSON with parameterized patterns showing how to dynamically construct payloads based on actual swarm state

Extract delegation patterns and emergency protocols into separate referenced files, keeping SKILL.md as a concise overview with clear navigation links

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 metaphorical language (morale, rebellious agents, hive loyalty) wastes tokens on concepts Claude doesn't need explained in narrative form.	1 / 3
Actionability	Contains concrete MCP tool call examples with specific JSON payloads, which is useful. However, the code blocks are store-only operations (writing static JSON to memory) with hardcoded placeholder values rather than dynamic, executable patterns. Many sections like 'Emergency Protocols' and 'Governance Protocols' are just bullet-point lists with no concrete implementation.	2 / 3
Workflow Clarity	No clear multi-step workflow with validation checkpoints. The 'Command Protocols' section lists abstract sequences (Issue directive → Monitor compliance → Evaluate results) without concrete steps. There are no feedback loops, error handling, or verification steps for any of the coordination operations. For an orchestrator managing destructive/batch operations across a swarm, this is a significant gap.	1 / 3
Progressive Disclosure	Monolithic wall of content with no references to external files. All content is inline regardless of complexity. The document is over 150 lines with sections that could be split (delegation patterns, emergency protocols, governance modes) but aren't. No navigation aids or cross-references.	1 / 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: 01070ed

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.