contacting-orchestrators
Skill5 starsChanged 54 days agoMITView on GitHub
Use before this session's first dispatch, and whenever another main agent's work meets this one's.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-feedbackSkill
- asking-peer-agentsSkill
- boss-assistantSkill
- boss-saySkill
- bringing-coworkerSkill
- choosing-graphSkill
- create-great-harnessSkill
- dispatching-workSkill
- handoff-orchestratorSkill
- i-am-orchestratorSkill
- initSkill
- notifying-main-agentSkill
- peeking-workSkill
- reporting-to-userSkill
- resolving-appSkill
- shipping-taskSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 15
Use live directory rows to resolve names or panes.
- Distinctive: line 33
Verify the premises of your own actions, such as whether the required commit has landed on the integration branch.
≈ “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.
Files
Register and find peers
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/register-orchestrator.py" \
--scope '<one line describing this main agent’s work>'
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/register-orchestrator.py" --listRegister before the first dispatch and update the record when scope changes.
Use live directory rows to resolve names or panes.
A live: false row carries an unavailable_reason; a discovered row can receive messages before declaring its own scope.
Any live agent with a verified session sends and receives messages without registering; registration adds its declared scope to the directory.
A pane with no verified identity remains unattributed.
Exchange a delta
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/send-orchestrator-message.py" \
--to <name-or-pane> --intent inform|question|answer \
--message '<delta>' [--ref '<source>'] [--in-reply-to <id>]Send one fact, question, or answer in at most two sentences; repeat --ref for supporting material.
Reply to the incoming sender using its question id.
Transport validates recipient identity and records delivery failures.
Accept a peer's conclusions within its owned scope. Verify the premises of your own actions, such as whether the required commit has landed on the integration branch. Conflicting facts go to the user; each task retains its current direction.
Route Straw Boss friction through boss-assistant.
Complete when: this session's scope is current and each owed delta is delivered or recorded undelivered.
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
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.