agentleFS
Sign inStart free
jmporchetjmporchet/pstack-hermes/skills/swarm/SKILL.md

swarm

Skill2 starsChanged 2 months agoMITView on GitHub

Fan out N parallel workers, drain them, and return one report. Use for `pstack:swarm`, 'swarm this', or parallel coverage, races, gauntlets, and exploration.

87 other projects use a version of this, 45 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use poteto-help, principle-explain-the-number and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 27 projects that use this

  • jaydubya818Skill

    principle-attack-the-premise

    Apply when repeated fixes fail and a shared assumption may be wrong.

    Also in 31 projects that use this

  • jaydubya818Skill

    principle-test-behavior-not-implementation

    Apply when tests mirror internals instead of asserting observable outcomes.

    Also in 31 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 11 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 83 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the active Hermes session model and delegation configuration.

    line 24
  2. Distinctive:

    When a worker must start from a non-default branch, include the branch name in its self-contained goal and verify the checkout before …

    line 31
  3. Very specific:

    Every brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report.

    line 33
  4. Distinctive:

    If a worker drops out, proceed with N-1 and note it.

    line 35
  5. Distinctive:

    Read the terminal results.

    line 39
  6. Distinctive:

    Keep a compact result table, one-line evidenced issues, and explicit gaps or dropouts.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 83 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swarm

Fan out N parallel cloud workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report.

Start

Open a todolist with one entry per phase before launching anything.

  1. Frame
  2. Fan out
  3. Aggregate
  4. Report

Phase A: Frame

  1. State the done predicate and the artifact or report the swarm must return.
  2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare first pass, rank all, or best-of before spawning.
  3. Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit.
  4. Use the active Hermes session model and delegation configuration. Do not invent a per-worker model parameter. For comparisons, state the intended comparison explicitly and run separate Hermes processes only when distinct models are genuinely required.
  5. Give each worker its own writable output when it writes. Use a worktree, branch, or /tmp/swarm-<slug>/worker-<n>/.

Phase B: Fan out

Spawn all N workers with delegate_task in one assistant turn when independent. Each brief stands alone. Include the goal, scope, exact slice or race arm, verification command, and report format.

When a worker must start from a non-default branch, include the branch name in its self-contained goal and verify the checkout before editing.

Every brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use PASS, ISSUES, or BLOCKED with evidence.

If a worker drops out, proceed with N-1 and note it.

Phase C: Aggregate

Read the terminal results. For coverage, every required slice needs a result. For a race, apply the selection rule declared up front. Use first pass, rank all, or best-of. Do not paste raw worker dumps.

Keep a compact result table, one-line evidenced issues, and explicit gaps or dropouts.

Phase D: Report

Return one consolidated in-chat report with the table, issue one-liners, gaps or dropouts, and the race rule when used.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free