agentleFS
theseus-runtheseus-run/theseus/.agents/skills/dispatch-satellite/SKILL.md

dispatch-satellite

Skill1 starsChanged 6 months agoMITView on GitHub

Use when working on the Theseus dispatch loop, dispatch store, tool-call execution, satellite middleware, dispatch events, or intervention policy in packages/theseus-core/src/dispatch and packages/theseus-core/src/satellite.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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 this skill for dispatch-loop and satellite middleware changes.

    line 8
  2. Distinctive:

    Keep dispatch headless. UI and operator transport belong outside core.

    line 28
  3. Distinctive:

    Keep satellite state scoped to one dispatch.

    line 32
  4. Distinctive:

    Run focused dispatch/satellite tests after behavioral changes:

    line 38
  5. Very specific:

    Run bun run typecheck when public event, decision, or store types change.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Dispatch And Satellite

Use this skill for dispatch-loop and satellite middleware changes.

Read First

  • packages/theseus-core/src/Dispatch.ts
  • packages/theseus-core/src/dispatch/dispatch.ts
  • packages/theseus-core/src/dispatch/step.ts
  • packages/theseus-core/src/satellite/types.ts
  • packages/theseus-core/src/satellite/ring.ts

Terms

  • Dispatch: the model/tool loop that turns a task and spec into events and final output.
  • Satellite: dispatch-scoped observation and policy middleware.
  • SatelliteRing: ordered static middleware configuration.
  • SatelliteScope: per-dispatch state and resources opened from the ring.
  • RuntimeBus: operator/client transport concept. Do not use it as a synonym for Satellite.

Rules

  • Keep dispatch headless. UI and operator transport belong outside core.
  • Satellites may observe, transform, block, replace, recover, or abort through typed decisions.
  • Satellites must not smuggle direct mailbox writes or hidden side channels into the dispatch loop.
  • Preserve ordered ring semantics: non-terminal decisions feed later satellites.
  • Keep satellite state scoped to one dispatch. Do not put per-dispatch mutable state on the static ring.
  • Preserve event shapes used by server/client serialization unless deliberately migrating them.
  • Convert SatelliteAbort at the dispatch boundary according to the existing dispatch error model.

Verification

  • Run focused dispatch/satellite tests after behavioral changes:
    • bun test packages/theseus-core/src/dispatch
    • bun test packages/theseus-core/src/satellite
  • Run bun run typecheck when public event, decision, or store types change.

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.