swarm

Fan out N parallel cloud workers and aggregate results into one consolidated report.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill swarm-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swarm
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/pstack/skills/swarm
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill swarm-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple parallel AI workers manually leads to inconsistent briefs, lost results, and unclear completion criteria. This Skill structures parallel fan-out so every worker gets a standalone brief, results are aggregated against a declared done predicate, and gaps or dropouts are reported honestly instead of guessed. ## Core Features & Use Cases - Structured Fan-Out: Spawn N cloud workers in one message with standalone briefs covering goal, scope, verification, and reporting format. - Three Shapes: Partition work into slices, race N workers on identical briefs with a declared selection rule (first pass, rank all, best-of), or mix both. - HOLD Discipline: Stop and report missing inputs (done predicate, worker count, output separation) rather than inventing assumptions. - Use Case: Ask to swarm a codebase audit across five modules; each worker covers one slice, reports PASS/ISSUES/BLOCKED with evidence, and you receive one compact table with issues and explicit gaps. ## Quick Start Ask the agent to swarm this task with four parallel workers, each covering a separate module, and return one consolidated report.

Frequently Asked Questions about swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel AI workers on a task?▼

Define a done predicate, choose a shape (partition, race, or mix), set the worker count N, and spawn all workers in one message with standalone briefs. Each brief includes the goal, scope, verification method, and a PASS/ISSUES/BLOCKED report format.

What is the difference between partition and race shapes in a swarm?▼

Partition splits work into separate slices so each worker covers distinct scope. Race gives N workers identical briefs and applies a declared selection rule (first pass, rank all, or best-of) to pick the winning result.

When should I not use a parallel worker swarm?▼

Avoid swarming when a single sequential investigation suffices, when no falsifiable done predicate can be stated, or when workers would write to the same shared path without separate output locations.

What happens when a swarm worker drops out or gets blocked?▼

Proceed with N-1 workers and note the dropout explicitly in the final report. If all workers are blocked, report BLOCKED rather than inventing consolidated success or faking a PASS.

How are race results selected between multiple workers?▼

The selection rule must be declared before spawning: first pass, rank all, or best-of. Contradictory race results are never averaged without a declared rule, and the applied rule is stated in the final report.