Agent skill for multi-repo-swarm - invoke with $agent-multi-repo-swarm
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-multi-repo-swarm43
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 — 87%
↑ 4.34xAgent success when using this skill
Validation for skill structure
Batch dependency update coordination
Tracking issue first
0%
100%
Tracking issue labels
0%
100%
Shallow clone flag
0%
100%
Change detection before PR
0%
0%
Date-stamped branch name
0%
0%
PR automation label
0%
100%
Tracking issue reference in PR
0%
100%
PR URL accumulation
50%
100%
Link PRs with ruv-swarm
0%
0%
Failure reporting to issue
0%
100%
Eventual consistency for deps
0%
0%
Without context: $0.2657 · 1m 29s · 13 turns · 19 in / 4,996 out tokens
With context: $0.4459 · 1m 39s · 19 turns · 179 in / 5,690 out tokens
Multi-repo swarm config and initialization
Correct config file path
0%
100%
Config version field
0%
100%
Repo role field
100%
100%
Repo agents field
100%
100%
Correct agent types per role
0%
100%
Hierarchical topology
0%
100%
Webhook communication
0%
100%
Redis shared memory
25%
100%
Dependencies section
30%
100%
Init uses --shared-memory
0%
100%
Init uses --topology hierarchical
0%
100%
Without context: $0.3473 · 1m 46s · 17 turns · 70 in / 6,538 out tokens
With context: $0.3933 · 1m 16s · 19 turns · 22 in / 4,016 out tokens
Security patch with strong consistency
Auth pre-check
100%
100%
Repo access pre-check
75%
100%
Uses ruv-swarm security command
0%
100%
--scan-all flag
0%
100%
--patch-vulnerabilities flag
0%
100%
--verify-fixes flag
0%
100%
--compliance-report flag
0%
100%
Strong consistency strategy
0%
100%
Raft consensus
0%
100%
Quorum setting
100%
100%
Does NOT use eventual consistency
100%
100%
Without context: $0.3556 · 1m 56s · 12 turns · 17 in / 7,614 out tokens
With context: $0.4722 · 1m 53s · 19 turns · 24 in / 6,204 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.