Agent skill for sync-coordinator - invoke with $agent-sync-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-sync-coordinator31
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/skillValidation for skill structure
Swarm initialization and agent spawning
swarm_init called
100%
100%
topology specified
100%
100%
maxAgents specified
100%
100%
coordinator agent spawned
100%
100%
analyst agent spawned
100%
100%
coder agent spawned
100%
100%
tester agent spawned
100%
100%
task_orchestrate with strategy
100%
100%
TodoWrite progress tracking
0%
100%
memory_usage store
0%
100%
memory key structure
0%
100%
memory timestamp field
0%
100%
Without context: $1.1853 · 4m 3s · 48 turns · 1,155 in / 14,778 out tokens
With context: $0.4841 · 1m 52s · 17 turns · 273 in / 6,994 out tokens
Documentation sync with gh CLI and memory state
gh CLI for branch creation
100%
100%
gh CLI for file update
100%
100%
load_balance called
100%
100%
source-of-truth respected
100%
100%
memory stores doc status
40%
100%
memory key for docs
100%
100%
post-sync validation
0%
60%
sync report generated
100%
100%
swarm_init present
100%
100%
agent types present
100%
100%
Without context: $0.4446 · 2m 8s · 17 turns · 23 in / 8,243 out tokens
With context: $0.6113 · 2m 23s · 20 turns · 23 in / 8,716 out tokens
Batch atomic commits and sync metrics storage
push_files for batch commit
0%
100%
metrics stored in memory
0%
50%
metrics version_alignment_score
0%
100%
metrics integration_test_success_rate
0%
50%
metrics documentation_sync_percentage
0%
0%
conflict resolution by impact
100%
100%
resolution_strategy field
0%
100%
rollback mechanism present
20%
0%
swarm_init + agent_spawn
50%
100%
task_orchestrate with dependencies
0%
20%
coordination_sync called
0%
100%
Without context: $0.3775 · 1m 52s · 15 turns · 21 in / 7,513 out tokens
With context: $0.4207 · 1m 33s · 18 turns · 180 in / 4,915 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.