swarm-advanced
Orchestrate Advanced Multi-Agent Swarms
Complex projects need coordinated agents, dependencies, memory, and recovery. This skill provides reusable Claude Flow patterns for research, development, testing, analysis, and monitoring.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "swarm-advanced" from https://skillstore.io/skills/ruvnet-swarm-advanced.md and its manifest at https://skillstore.io/api/skills/ruvnet-swarm-advanced/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "swarm-advanced". Plan a swarm to research current database options for a regulated application.
Expected outcome:
- Topology: mesh with two researchers, one compliance analyst, one performance analyst, and one report writer.
- Flow: gather sources in parallel, validate evidence, compare constraints, then synthesize a cited recommendation.
- Controls: use approved sources, record uncertainty, and exclude unsupported product claims.
Using "swarm-advanced". Coordinate delivery of account recovery for an existing web application.
Expected outcome:
- Topology: hierarchical with an architect coordinating backend, frontend, database, testing, security review, and documentation roles.
- Dependencies: approve threat model first, implement components in parallel, then complete integration tests and review.
- Result: a staged delivery plan with owners, acceptance criteria, checkpoints, and rollback requirements.
Using "swarm-advanced". Create a recovery plan for a testing swarm that fails during parallel execution.
Expected outcome:
- Pause dependent tasks and capture current state, logs, and completed results.
- Assess swarm health, isolate the failed task, and retry it sequentially with a bounded attempt limit.
- Restore the latest checkpoint when state is inconsistent, then report the failure cause and recovery outcome.
Security Audit
SafeMost alerts are false positives caused by Markdown fences, inline names, documentation links, and ordinary guidance. Four findings are confirmed because examples execute community npm packages through global installation or unversioned npx commands. No prompt injection, exfiltration intent, or malicious behavior was found.
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/ruvnet-swarm-advanced/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/ruvnet-swarm-advanced?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/ruvnet-swarm-advanced?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ruvnet-swarm-advanced/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/ruvnet-swarm-advanced.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
ruvnet. (2026). swarm-advanced security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/ruvnet-swarm-advanced/audits/8BibTeX citation
@techreport{ruvnet-ruvnet-swarm-advanced-2026,
author = {ruvnet},
title = {swarm-advanced security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/ruvnet-swarm-advanced/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "swarm-advanced security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "ruvnet"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/ruvnet-swarm-advanced/audits/8"
identifiers:
- type: other
value: "skillstore:ruvnet-swarm-advanced:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
dnyoussef-swarm-advanced
2026-09-09
ruvnet-swarm-advanced
2026-09-09
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Coordinate Parallel Research
Assign source discovery, validation, analysis, and synthesis to specialized agents, then combine results into a structured report.
Deliver a Full-Stack Feature
Coordinate architecture, backend, frontend, database, testing, review, documentation, and deployment tasks with explicit dependencies.
Run Distributed Quality Analysis
Parallelize unit, integration, performance, and security checks while centralizing monitoring and final reporting.
Try These Prompts
Create a mesh swarm plan for [research topic]. Define agent roles, parallel tasks, validation steps, dependencies, and the final report structure.
Design a hierarchical swarm for [feature]. Assign architecture, implementation, testing, review, and documentation tasks with clear dependencies and completion criteria.
Plan a star-topology testing swarm for [system]. Cover unit, integration, end-to-end, performance, and security testing with monitoring and reporting.
Design a reusable swarm workflow for [objective]. Include topology changes, memory namespaces, checkpoints, retries, scaling rules, metrics, failure recovery, and approval boundaries.
Best Practices
- Define deliverables, dependencies, and completion criteria before spawning agents.
- Assign distinct roles with bounded permissions, shared state rules, and named owners.
- Start with the smallest useful swarm, monitor resource use, and scale only when evidence supports it.
Avoid
- Do not assign duplicate responsibilities without a clear review or reconciliation process.
- Do not enable production deployment or persistent automation without explicit user approval.
- Do not place secrets, credentials, or sensitive personal data in shared swarm memory.