swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
50
24%
Does it follow best practices?
Impact
100%
3.84xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/swarm-advanced/SKILL.mdQuality
Discovery
22%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 too abstract and buzzword-heavy, reading more like a marketing tagline than a functional skill description. It fails to specify concrete actions the skill performs and entirely lacks explicit trigger guidance ('Use when...'). The domain of 'swarm orchestration' is somewhat distinctive but is undermined by overly broad qualifying terms.
Suggestions
Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user asks to coordinate multiple agents, run parallel research tasks, or orchestrate distributed sub-agent workflows.'
Replace vague language with concrete actions, e.g., 'Spawns and coordinates multiple sub-agents for parallel task execution, aggregates results, manages agent communication and error handling.'
Narrow the scope terms—'research, development, testing' are too broad. Specify what kinds of research or testing workflows this handles to reduce conflict with general dev/test skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'advanced swarm orchestration patterns' and 'complex distributed workflows' without listing any concrete actions. No specific operations (e.g., 'spawn agents', 'coordinate tasks', 'aggregate results') are mentioned. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (swarm orchestration patterns) and completely lacks a 'when' clause or any explicit trigger guidance. There is no 'Use when...' or equivalent. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'swarm', 'orchestration', 'research', 'development', 'testing', and 'distributed workflows', but these are broad and somewhat jargon-heavy. A user might say 'swarm' or 'orchestration' but the terms lack natural variation and specificity. | 2 / 3 |
Distinctiveness Conflict Risk | While 'swarm orchestration' is somewhat niche, the broad terms 'research', 'development', 'testing', and 'complex distributed workflows' could easily overlap with many other skills related to development, testing, or workflow management. | 2 / 3 |
Total | 6 / 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 extremely verbose and repetitive, presenting four nearly identical swarm patterns with full boilerplate code that could be condensed to a single template with variations. While it provides concrete tool calls, many reference undefined variables and appear to be aspirational rather than verified working code. The content would benefit enormously from splitting into separate files per pattern and adding validation checkpoints within workflows.
Suggestions
Reduce to ~150 lines by extracting each pattern (Research, Development, Testing, Analysis) into separate referenced files, keeping only a concise overview and one complete example pattern in the main SKILL.md
Remove undefined variables (findings, researchData, sourcesArray, etc.) and either provide complete self-contained examples or explicitly note what inputs are expected
Add explicit validation checkpoints between phases (e.g., 'Check swarm_status before proceeding to Phase 2; if any agent failed, re-spawn before continuing')
Eliminate the repetitive agent spawning boilerplate by showing it once with a note that the pattern applies to all topologies, varying only the agent definitions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 600+ lines with massive repetitive code blocks. The four swarm patterns (Research, Development, Testing, Analysis) follow nearly identical structures with redundant agent spawning boilerplate. Much of this could be condensed to a single pattern with variations noted. The topology descriptions, best practices, and troubleshooting sections explain concepts Claude already understands. | 1 / 3 |
Actionability | Provides concrete MCP tool calls and CLI commands, which is good. However, the code is not truly executable—it uses undefined variables (findings, researchData, sourcesArray, testSuites, workflowMetrics), mixes async/await with synchronous patterns inconsistently, and many tool calls appear to be aspirational API designs rather than verified working commands. The CLI fallback commands are the most actionable parts. | 2 / 3 |
Workflow Clarity | Each pattern has clear phased workflows (Phase 1-4) with logical sequencing. However, there are no explicit validation checkpoints or feedback loops between phases—no 'verify Phase 1 output before proceeding to Phase 2' steps. The error handling section exists but is generic and separate from the workflows rather than integrated into them. For complex distributed operations, the lack of verification gates is a significant gap. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all four patterns fully expanded inline. The 'Related Skills' and 'References' sections at the bottom hint at external resources but the main content should have been split—each pattern could be its own referenced file. There's no clear overview-then-drill-down structure; instead everything is dumped at the same level of detail. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (974 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- ruvnet/agentic-flow
- Commit
8db2712
- 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.