swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
47
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
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, failing to specify concrete actions or provide trigger guidance. It reads like a marketing tagline rather than a functional skill description. The lack of explicit 'when to use' guidance and vague capability statements make it difficult for Claude to reliably select this skill.
Suggestions
Add a 'Use when...' clause with specific trigger scenarios, e.g., 'Use when the user needs to coordinate multiple agents, run parallel research tasks, or orchestrate distributed testing workflows'
Replace abstract language with concrete actions, e.g., 'Spawns and coordinates multiple sub-agents, manages parallel task execution, aggregates results from distributed workers'
Include natural user phrases that would trigger this skill, such as 'multi-agent', 'parallel agents', 'swarm of agents', 'coordinate tasks across agents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language like 'advanced swarm orchestration patterns' and 'complex distributed workflows' without listing any concrete actions. No specific capabilities like 'spawn agents', 'coordinate tasks', or 'manage parallel execution' are mentioned. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (orchestration patterns for various domains) and completely lacks any 'when' guidance. There is no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('research', 'development', 'testing', 'swarm', 'orchestration') but these are fairly generic. Missing natural user phrases like 'multi-agent', 'parallel tasks', 'coordinate agents', or specific workflow types users might request. | 2 / 3 |
Distinctiveness Conflict Risk | While 'swarm orchestration' is somewhat distinctive, the broad domains listed (research, development, testing) could overlap with many other skills. The term 'distributed workflows' is generic enough to conflict with other workflow-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable code examples for swarm orchestration patterns, which is its primary strength. However, it suffers from severe verbosity—the content could be reduced by 60-70% while preserving all essential information. The lack of integrated validation steps in workflows and the monolithic structure detract from usability.
Suggestions
Consolidate the four nearly-identical pattern sections (Research, Development, Testing, Analysis) into a single template with a configuration table showing topology/agent differences
Move Advanced Techniques, Best Practices, and Troubleshooting to separate referenced files (ADVANCED.md, BEST-PRACTICES.md) and keep only a quick-start overview in the main skill
Add explicit validation checkpoints within each workflow phase (e.g., 'Verify swarm_status shows all agents healthy before proceeding to Phase 2')
Remove explanatory text about what topologies are—provide only the selection guidance table since Claude understands these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines with extensive repetition of similar patterns. Much content explains concepts Claude already knows (what mesh topology is, basic error handling patterns) and includes redundant examples that could be consolidated. | 1 / 3 |
Actionability | Provides fully executable code examples with specific MCP tool calls, CLI commands, and complete JavaScript snippets. Examples are copy-paste ready with concrete parameters and realistic configurations. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with phases (Phase 1, 2, 3, 4), but lacks explicit validation checkpoints and error recovery feedback loops within the workflows. The error handling section exists but is separate from the main workflow patterns. | 2 / 3 |
Progressive Disclosure | References related skills and external documentation at the end, but the main content is a monolithic wall of code examples. Advanced techniques, best practices, and troubleshooting could be split into separate files with clear navigation from a concise overview. | 2 / 3 |
Total | 8 / 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 | |
- 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.