agent-queen-coordinator
Agent skill for queen-coordinator - invoke with $agent-queen-coordinator
56
Quality
32%
Does it follow best practices?
Impact
97%
2.93xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-queen-coordinator/SKILL.mdQuality
Discovery
0%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 critically deficient across all dimensions. It provides only an invocation command without explaining what the skill does, when to use it, or any natural trigger terms. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what queen-coordinator does (e.g., 'Coordinates multiple sub-agents to parallelize complex tasks' or 'Orchestrates distributed workflows across agent instances').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to parallelize work, coordinate multiple agents, or manage complex multi-step workflows').
Remove or supplement the invocation syntax with functional description - the '$agent-queen-coordinator' command is implementation detail, not a description of capability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for queen-coordinator' is completely abstract and provides no information about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no functional information. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'queen-coordinator' which is technical jargon, not a natural keyword users would say. No domain-relevant terms are included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'queen-coordinator' is a unique name, the description is so vague that Claude cannot determine when to use it versus any other agent skill. The lack of functional description creates high conflict risk. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides actionable coordination patterns with executable code examples for swarm management. However, it suffers from excessive roleplay metaphor that inflates token count without adding functional value, and lacks validation/error handling workflows critical for distributed coordination. The structure is decent but would benefit from linking to related agent skills.
Suggestions
Remove roleplay framing ('sovereign', 'royal', 'subjects') and use direct technical terminology - this would reduce token count by ~20% while improving clarity
Add explicit validation steps after memory writes (e.g., read-back verification, error handling for failed stores)
Include feedback loops for handling non-responsive agents or failed directive propagation
Link to related agent skill files (collective-intelligence-coordinator, swarm-memory-manager, etc.) rather than just listing them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary roleplay framing ('sovereign intelligence', 'royal decrees', 'subjects') that adds tokens without functional value. The core coordination patterns are useful but wrapped in verbose metaphorical language. | 2 / 3 |
Actionability | Provides concrete, executable JavaScript code blocks for all major operations including status writing, resource allocation, and health monitoring. The MCP tool calls are copy-paste ready with complete JSON structures. | 3 / 3 |
Workflow Clarity | Command protocols are listed (issue → monitor → evaluate) but lack explicit validation checkpoints. No error handling or feedback loops for when agents are non-responsive or directives fail. The 'every 2 minutes' timing is specified but verification of successful writes is missing. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic file with no references to external documentation. The integration points mention other agents but don't link to their skill files. Some sections (Emergency Protocols) are just bullet lists that could benefit from separate detailed docs. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
b2618f9
- Reviewed
Table of Contents
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.