agent-v3-queen-coordinator
Agent skill for v3-queen-coordinator - invoke with $agent-v3-queen-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-v3-queen-coordinator43
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 6.25xAgent success when using this skill
Validation for skill structure
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 functions only as an invocation reference rather than a skill description, providing no information about capabilities, use cases, or trigger conditions. Without knowing what 'v3-queen-coordinator' does, Claude cannot make informed decisions about when to select this skill.
Suggestions
Add concrete actions describing what this coordinator skill does (e.g., 'Orchestrates multi-agent workflows, delegates tasks to worker agents, manages parallel execution').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when coordinating complex tasks, managing multiple agents, or orchestrating parallel workflows').
Remove or relocate the invocation syntax ('invoke with $agent-v3-queen-coordinator') to a separate field, and replace with functional description content.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for v3-queen-coordinator' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | Fails to answer both 'what does this do' and 'when should Claude use it'. The description only provides an invocation syntax with no functional information. | 1 / 3 |
Trigger Term Quality | Contains only technical jargon ('v3-queen-coordinator') and an invocation command. No natural keywords a user would say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | While the name 'v3-queen-coordinator' is unique, the description provides no context about its purpose, making it impossible to distinguish from other skills based on user intent. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a project overview document than actionable agent instructions. It describes the organizational structure and timeline but fails to provide concrete coordination commands, inter-agent communication protocols, or decision-making workflows. The Queen Coordinator needs explicit instructions on how to dispatch tasks, monitor agent status, handle conflicts, and validate progress.
Suggestions
Add concrete coordination commands showing how to dispatch tasks to specific agents (e.g., actual CLI commands or API calls)
Include a workflow section with explicit steps for monitoring agent status, handling blocked agents, and resolving conflicts between agents
Add validation checkpoints for phase transitions (e.g., 'Before Phase 2: verify all security agents report green status')
Reference external files for detailed ADR specifications and individual agent protocols rather than keeping everything abstract
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some useful structure but contains verbose ASCII diagrams and repetitive phase breakdowns that could be condensed. The metrics and agent topology information is useful but presented with more ceremony than necessary. | 2 / 3 |
Actionability | The skill describes organizational structure and phases but provides no concrete commands, code examples, or executable guidance for how the Queen Coordinator actually coordinates agents. It's entirely descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | While phases are listed, there are no actual workflow steps, validation checkpoints, or feedback loops. The content describes what agents do in each phase but not how the coordinator orchestrates them or handles failures. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections (topology, phases, metrics) but lacks references to detailed documentation for each agent or ADR. Everything is inline with no clear navigation to deeper resources. | 2 / 3 |
Total | 6 / 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.
- 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.