Agent skill for swarm-issue - invoke with $agent-swarm-issue
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-swarm-issue45
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 — 97%
↑ 2.93xAgent success when using this skill
Validation for skill structure
Issue swarm infrastructure setup
Workflow issue triggers
70%
100%
Swarm-ready conditional
20%
100%
Template topology dropdown
100%
100%
All four topology options
70%
100%
Required agents field
25%
100%
Task breakdown field
28%
100%
Label rules array structure
70%
100%
Bug keyword mapping
60%
100%
Feature keyword mapping
60%
100%
Performance keyword mapping
50%
100%
Agent type assignments
0%
100%
Without context: $0.9869 · 3m 47s · 29 turns · 729 in / 8,829 out tokens
With context: $0.6585 · 2m 4s · 26 turns · 284 in / 7,257 out tokens
Issue decomposition and progress tracking
Decompose command used
0%
100%
max-subtasks flag
0%
100%
assign-priorities flag
0%
100%
Checkbox format
100%
100%
High-priority child issues
100%
100%
Parent issue back-reference
100%
100%
Subtask label
0%
100%
update-checklist command
0%
100%
Progress comment header
0%
100%
Emoji task sections
0%
100%
Automated update footer
0%
100%
Completion label swap
30%
100%
Without context: $0.4954 · 2m 8s · 29 turns · 34 in / 7,282 out tokens
With context: $0.4319 · 1m 26s · 20 turns · 434 in / 4,412 out tokens
Multi-agent swarm initialization and memory
swarm_init call
50%
100%
Bug uses hierarchical
0%
100%
Feature uses mesh
0%
100%
Docs uses ring
0%
100%
Bug agent roster
50%
100%
Feature agent roster
50%
0%
Docs agent roster
50%
100%
memory_usage store context
50%
100%
Memory key format
0%
100%
task_orchestrate call
0%
100%
adaptive strategy
0%
100%
Completion metrics stored
0%
100%
Without context: $1.6021 · 6m 35s · 62 turns · 58 in / 16,601 out tokens
With context: $0.2638 · 1m · 11 turns · 171 in / 3,418 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.