agent-multi-repo-swarm

Agent skill for multi-repo-swarm - invoke with $agent-multi-repo-swarm

4.34x

Quality

Does it follow best practices?

Impact

87%

4.34x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-multi-repo-swarm/SKILL.md

Quality

Discovery

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 critically deficient across all dimensions. It functions as little more than a label and invocation command, providing no information about what the skill does, when to use it, or what distinguishes it from other skills. It would be nearly impossible for Claude to correctly select this skill from a pool of available options.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Coordinates changes across multiple Git repositories, synchronizes dependencies, and manages cross-repo pull requests.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to make coordinated changes across multiple repositories, sync dependencies between repos, or manage multi-repo workflows.'

Include natural keywords users would actually say, such as 'multiple repositories,' 'cross-repo changes,' 'monorepo,' 'multi-project,' 'coordinated commits,' etc.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for multi-repo-swarm' is entirely vague—it doesn't describe what the skill actually does, only that it's an 'agent skill' with a name.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides an invocation command ($agent-multi-repo-swarm) but no explanation of purpose or trigger conditions.	1 / 3
Trigger Term Quality	The only potentially relevant term is 'multi-repo-swarm,' which is a technical/internal name rather than a natural keyword a user would say. There are no natural trigger terms like 'multiple repositories,' 'cross-repo,' 'coordinate changes,' etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's impossible to distinguish it from any other agent or multi-repo skill. Without concrete actions or scope, it could conflict with any repository-related skill.	1 / 3
	Total	4 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is an extremely verbose, largely aspirational document that describes a fictional multi-repo swarm orchestration system. Most commands are non-executable (referencing non-existent 'npx ruv-swarm github' subcommands), the bash examples contain path syntax errors, and the document is a monolithic wall of text with no meaningful progressive disclosure. The skill would need to be fundamentally rewritten to focus on actual, executable workflows.

Suggestions

Remove all fictional 'npx ruv-swarm github' commands and replace with actual executable workflows using the MCP tools listed in the frontmatter (mcp__claude-flow__swarm_init, etc.) and gh CLI

Fix path syntax errors throughout (e.g., 'repos$org/$repo' should be 'repos/org/repo', '$dev$null' should be '/dev/null')

Reduce to under 100 lines focusing on 2-3 core workflows with explicit validation steps, and move advanced topics to separate referenced files

Add explicit validation checkpoints and error recovery steps for the batch operations (e.g., verify PR creation succeeded, handle clone failures, validate test results before proceeding)

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines with massive amounts of speculative/aspirational content. Most CLI commands (npx ruv-swarm github ...) appear to be fictional/non-existent tools, and the skill includes extensive configuration examples for systems like Kafka, GraphQL federation, Redis, and webhook coordinators that are unlikely to be actionable. Huge amounts of redundant sections (troubleshooting, performance, monitoring) that add little value.	1 / 3
Actionability	The vast majority of commands reference 'npx ruv-swarm github' subcommands that appear to be fictional and non-executable. The bash scripts in sections 1-3 have syntax issues (using $ instead of / in paths like 'repos$org/$repo$contents$package.json'). The few potentially real commands (gh CLI usage) are buried among non-functional examples, making the skill largely unusable as concrete guidance.	1 / 3
Workflow Clarity	While some sections like 'Synchronized Operations' and 'Dependency Management' attempt multi-step workflows, they lack validation checkpoints and error recovery. The dependency update section has a basic test-before-PR pattern but no validation of the overall process. Most sections are just single CLI invocations with no sequencing. No feedback loops for the many destructive/batch operations described.	1 / 3
Progressive Disclosure	Monolithic wall of text with 20+ sections all inline. Content that should be in separate files (communication strategies, synchronization patterns, configuration examples, troubleshooting) is all crammed into one massive document. The only cross-references are two links at the very bottom. The sheer volume makes navigation extremely difficult.	1 / 3
	Total	4 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: ruvnet/ruflo
Commit: 398f7c2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.