agent-multi-repo-swarm
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
Discovery
7%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 severely deficient, functioning more as a label than a useful description. It provides no information about what the skill does, when to use it, or what problems it solves. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Coordinates changes across multiple git repositories, synchronizes branches, manages cross-repo dependencies').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when working across multiple repositories, coordinating multi-repo changes, or managing monorepo-style workflows').
Remove or relocate the invocation syntax ('invoke with $agent-multi-repo-swarm') to the skill body, as it doesn't help Claude decide when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for multi-repo-swarm' is completely abstract and doesn't describe what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description only provides a name and invocation syntax, with no explanation of capabilities or usage triggers. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('agent skill', 'multi-repo-swarm') and an invocation command. No natural keywords a user would say when needing this functionality. | 1 / 3 |
Distinctiveness Conflict Risk | The specific name 'multi-repo-swarm' and invocation command '$agent-multi-repo-swarm' provide some distinctiveness, but without knowing what it does, it's unclear what it might conflict with. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is severely bloated and tries to cover too much ground in a single file. While it contains some actionable gh CLI examples, much of the content relies on an undocumented 'ruv-swarm' tool and reads more like aspirational documentation than executable guidance. The lack of progressive disclosure and excessive verbosity make this difficult to use effectively.
Suggestions
Split content into separate files: core operations in SKILL.md, configuration reference in CONFIG.md, communication strategies in COMMUNICATION.md, and troubleshooting in TROUBLESHOOTING.md
Remove or clearly mark the 'npx ruv-swarm' commands as hypothetical/planned functionality, or document what this tool actually does
Reduce the main skill to essential workflows (repo discovery, synchronized operations, dependency management) with clear validation checkpoints
Add explicit error handling and validation steps to workflows involving destructive operations like creating PRs across multiple repos
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with massive redundancy. Many commands are variations of the same pattern (npx ruv-swarm github X). Includes extensive configuration examples, multiple sync strategies, and troubleshooting sections that could be in separate reference files. | 1 / 3 |
Actionability | Contains concrete bash commands and code examples, but relies heavily on a hypothetical 'ruv-swarm' CLI tool with undocumented behavior. The gh CLI examples are executable, but many npx commands appear to be pseudocode for non-existent functionality. | 2 / 3 |
Workflow Clarity | Some workflows like 'Synchronized Operations' show clear sequences with validation (checking git status, running tests before PR), but most sections are just command listings without explicit validation checkpoints or error recovery steps. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. Contains configuration examples, multiple communication strategies, advanced features, troubleshooting, and use cases all in one file. References to other files at the end but the main content desperately needs splitting. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (558 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.