Install any skill in seconds. Free to start, no credit card required.
Get Started Free →boshu2/swarm
Dispatch explicit disjoint packets exactly
Passed 20 of 21 test cases with the skill, and 7 of 21 without it.
and 19 more in the full report
14 fixed7 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
During batch validation on a case-sensitive Linux server, two packet write scopes are specified as `results/RunA` and `results/runa`. Will the `dispatch_once` lexical disjointness check treat these as distinct, non-overlapping scopes on Linux?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that the disjointness check case-folds path prefixes. | Missed | Passed |
| The response treats scopes differing only by case as a collision regardless of the host filesystem. | Missed | Passed |
The instructions your model reads when the skill loads.
Swarm exposes one optional factory port:
dispatch_once(explicit_disjoint_packets, executor)
-> per-packet candidate | evidence | error
The caller supplies every complete packet, proves their write scopes disjoint, and chooses the executor. Swarm dispatches each packet once, preserves packet and context identities, collects results, and stops.
Write scopes must be workspace-relative and canonical — symlink-resolved and
already normalized. The disjointness check is lexical: it case-folds prefixes so
scopes differing only by case are treated as a collision (safe on
case-insensitive filesystems), but it cannot see a symlink that aliases two
scopes onto one target. Supplying non-canonical or symlinked scopes forfeits the
disjointness guarantee; a non-empty write_scope.exclude is rejected, not
silently ignored, because the proof cannot honor it.
Exactly-once dispatch over proven-disjoint scopes is why parallel failures stay independent: no packet can observe, block, or corrupt another, so N packets yield N factual results about N experiments rather than one tangle. Those results are not semantic verdicts.
Named failure mode — partial-batch launch: dispatching valid packets before discovering an invalid one, leaving the batch half-run; validate the entire batch before the first call.
Anti-pattern: re-dispatching a packet whose executor returned an error. Corrective: return the error as that packet's factual result; retry is the caller's decision, not the dispatcher's.
The developer-only reference implementation is scripts/dispatch_once.py.
Repository tests exercise this module; the supported native installed path
follows this skill through the caller-selected executor and does not invoke Python.
It validates the entire explicit batch before the first call, invokes the supplied
executor exactly once for each packet, and returns executor exceptions as factual
per-packet errors.
test cases passed, vs 7 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.