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
Coordination lifecycle hooks
Intelligence stats command
0%
100%
Intelligence output to file
0%
100%
Intelligence fallback
0%
100%
GitHub CLI presence check
100%
100%
GitHub auth verification
100%
100%
Memory store-pattern command
0%
100%
Session ID with timestamp
0%
100%
Task parameter
0%
100%
Agent parameter
0%
100%
Status parameter
0%
100%
Silent error handling
0%
100%
Without context: $0.3901 · 1m 33s · 22 turns · 28 in / 5,537 out tokens
With context: $0.6023 · 1m 39s · 29 turns · 31 in / 5,595 out tokens
Agent swarm topology and phases
Queen orchestrator role
60%
100%
Security group size
0%
100%
Core group size
0%
100%
Integration group size
0%
100%
Specialist single agents
14%
100%
Total agent count
0%
100%
Hierarchical mesh topology
28%
100%
Phase 1 scope
0%
100%
Phase 2 scope
11%
100%
Phase 3 scope
11%
100%
Phase 4 scope
0%
100%
Coordinator concurrency constraint
0%
100%
Without context: $0.2750 · 1m 25s · 11 turns · 15 in / 5,426 out tokens
With context: $0.5214 · 1m 59s · 26 turns · 290 in / 6,884 out tokens
V3 performance targets and ADR scope
Parallel efficiency target
0%
100%
Flash Attention lower bound
0%
100%
Flash Attention upper bound
0%
100%
AgentDB search lower bound
0%
100%
AgentDB search upper bound
0%
100%
Memory reduction range
100%
100%
Code line count target
0%
100%
Baseline codebase size
0%
100%
ADR count
100%
100%
14-week timeline
0%
100%
4-phase structure
0%
100%
Without context: $0.3016 · 1m 42s · 15 turns · 19 in / 5,617 out tokens
With context: $0.5000 · 2m 8s · 22 turns · 284 in / 7,356 out tokens
Table of Contents
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.