agentleFS
DarthJonathanDarthJonathan/guac-skills/skills/swarm/SKILL.md

swarm

Skill0 starsChanged 18 days agoMITView on GitHub

Coordinate workers across distinct slices or a declared race and return one evidence-backed report. Use for swarm or parallel coverage requests.

87 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 83 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the Codex runtime adapter once per session before using this skill.

    line 6
  2. Distinctive:

    Use permitted native subagents and the swarm workers role, defaulting to inheritance.

    line 12

“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

Read the Codex runtime adapter once per session before using this skill. Its tool, model, history, and authorization mappings apply to all linked instructions.

Swarm

  1. Name the done condition and choose partitioned coverage, a race, or a mixture. For a race, declare first-pass, rank-all, or best-of before starting.
  2. Give each worker a distinct slice, output location, and verification contract. For commit comparisons, name exact SHAs. For measurements, specify what one sample is, the sampling method, and order.
  3. Use permitted native subagents and the swarm workers role, defaulting to inheritance. Do not invent cloud machines or unsupported spawn fields. Respect concurrency limits and isolate writers. Name each model actually used for a model race.
  4. Each worker returns PASS, ISSUES, or BLOCKED with evidence and all proven issues. Reject results missing the required artifact identity or measurement method. Retry a missing report once; after that, record a gap.
  5. For coverage, account for every required slice. For a race, apply the declared selection rule. Inspect important evidence yourself and integrate any changes coherently.

Return one consolidated report with results, proven issues, evidence, and gaps. If delegation is unavailable or prohibited, execute useful slices sequentially and label the execution mode. A coverage gap never becomes a pass.

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.