agentleFS
Phat-PoPhat-Po/multi-agent-orchestrator/skills/multi-agent-orchestrator/SKILL.md

multi-agent-orchestrator

Skill0 starsChanged 4 months agoMITView on GitHub

Coordinate an Atrium workspace through a decision agent, bounded role agents, local handoffs, and a live task dashboard. Use when a task benefits from a visible multi-agent workflow.

10 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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    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 local run created by the SessionStart hook when present.

    line 8
  2. Very specific:

    Read references/protocol.md for state and recovery rules.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 7 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

Multi-Agent Orchestrator

Use the local run created by the SessionStart hook when present. Read project governance before work and obey every approval gate.

  1. The decision agent owns the task contract and final decision.
  2. Roles write progress with progress.py; do not rely on chat history as state.
  3. The Canvas is status-only. It never authorizes an action.
  4. Roles may investigate while waiting, but must not mutate code, credentials, data, deployments, or remotes without the project's required approval.
  5. Read references/protocol.md for state and recovery rules.

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.