Individual skill
swarm
Fan out independent slices or coverage partitions and aggregate them with owner verification. Use for large audits, races, and parallel work.
skills/swarm/SKILL.md
Source commit 79595c97d47b5400034fb985e67f1a00389a81af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 22
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cursor Repository topic
- pstack Repository topic
- cline Repository topic
- copilot Repository topic
- gemini Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 714 bytes
Read excerpt
# Swarm
1. Define a partition with minimal shared mutable state and one owner per slice.
2. Give every worker exact scope, output schema, evidence requirements, and stop condition.
3. Use isolated `delegate` workers when available. If not, execute slices sequentially and label the fallback.
4. Collect artifacts and evidence, not only prose summaries.
5. The parent reconciles overlap, conflicts, and missing coverage, then independently checks high-impact findings or integrations.
6. Return one deduplicated result and a coverage map.