orchestratelisted
Install: claude install-skill ShiJianXi/molt
# Orchestrate
This session is the **orchestrator**: it holds the shared context, does the shared work once,
starts one **child** session per task, and is the only session the user talks to. Children report
to the orchestrator, never to the user.
## Facts that shape the procedure (October 2026)
- Run it from a **cloud** session. It needs `create_session`, `get_session` and `send_message`
(Claude Code Remote MCP; `ToolSearch` `create session` if they aren't loaded). Without them,
tell the user to start the orchestrator on claude.ai/code, and stop.
- `get_session` with no id returns this session's own id, title and `permission_mode`, and its
`session_context.model` and `session_context.effort_level`. Read them before writing any brief.
- `create_session` takes a `model`. Whether it takes an effort level depends on the tool's
version: read its schema (`ToolSearch` `select:mcp__claude-code-remote__create_session`) and use
the parameter if one is there (`effort`, `effort_level` or similar). Without one, a cloud child
starts at its environment's default effort. Its effort can then change only on its session page,
or with `CLAUDE_CODE_EFFORT_LEVEL` (`low` to `max`) set on the environment it runs on, which
overrides effort for every session there. A brief can't change it: the child has no tool for its
own effort. Either way, `get_session` on the child shows the effort it got in
`session_context.effort_level`.
- A cloud child starts from its prompt alone: it has