PabloTheThinkerPabloTheThinker/the-conductor-hermes/skills/conductor/batch-for-host/SKILL.md

batch-for-host

Skill1 starsChanged 4 months agoMITView on GitHub

Host tool batching vs Remnant fanout — wave A/B/C, hermes_batch, concurrency, anti-serial patterns.

In this repository5 other files it gives its agents.
- comboSkill
- pillarsSkill
- planSkill
- remnant-guideSkill
- reviewSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
No remnant fanout unless stuck
line 36

≈ “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

Batch for host (Conductor 1.18.10+)

Use when: multi-file reads, mixed edit turns, multi-axis clone spawn, or the agent is serializing tools unnecessarily.

Two parallelisms

	Host tool batch	Remnant / clones
Mechanism	Many tools in one turn	`hermes_batch` → `delegate_task(tasks=[…])` or Grok `spawn_subagent` ×N
Scheduler	Host (Hermes segments large mixed batches)	Parent + `delegation.max_concurrent_children`
Default	Thin mode / everyday work	Full mode, multi-surface, Combo C

Conductor never reimplements Hermes tool-batch segmentation.

Waves (advisory)

Wave	Class	Do
A	safe_parallel	Reads, status, doctor, search — fire together (`HOST_PARALLEL_SAFE` / `host_parallel_safe()`)
B	barrier	Writes, patch, terminal — host may segment; still emit in the same batch as A when possible
C	spawn	One `hermes_batch` / multi-`spawn_subagent` — not N serial parent turns

Module: conductor.core.wave_planner (classify_tool, plan_waves, host_parallel_safe).

Recipes

Thin (default)

conductor_start_pack / thin start
One mixed host batch (prefer large)
No remnant fanout unless stuck
Optional memory_episodic

Full multi-axis

Fanout → read tool_calls + hermes_batch
Parent spawns this turn (wave C) — do not only read the contract
spawn_ack → report → merge
Respect mandatory_host_action

Hybrid

Local/safe preflight (wave A findings in local_preflight)
Host deepen with preflight in context — do not re-scan the same paths

Concurrency (Hermes)

# $HERMES_HOME/config.yaml
delegation:
  max_concurrent_children: 6  # raise if hermes_batch size > default (often 3)

Check: conductor hermes-ready → delegation_concurrency.

Thrash + host kwargs (1.18.10)

record_and_check(store, session_id, tool_name, args=None, *, batch_id=None, wave_id=None)
Failure scars need host status/error_type or structured JSON — bare "error" in success dumps must not scar

Anti-patterns

Serialize whole turn because one write exists among many reads
N serial delegate_task when one tasks=[…] batch works
Fanout on single-file / kill-the-port work
Reimplementing host segmentation inside Conductor
Ritual-only: reading tool_calls without spawning
Scaring on content that merely contains the word “error”

docs/ORCHESTRATION.md — tool classes + waves
docs/HERMES.md — host batch vs Remnant
docs/HERMES_SUBAGENT_FANOUT.md — real multi-clone spawn
Skill remnant-guide — Combo C strategy (when to fanout)

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.

Check your setup, free