| name | yolobox-orchestrator |
| description | Use when the agent is outside yolobox and needs to start, inspect, or control yolobox sessions, choose the right yolobox subcommand or flags, read merged config, decide between scratch, readonly, docker, or network options, or debug how a yolobox launch should be configured. |
| license | MIT |
| compatibility | Requires the yolobox CLI on the host. Runtime behavior depends on the configured container runtime and local Docker, Podman, or Apple container access. |
Yolobox Orchestrator
Use this skill for host-side orchestration of yolobox sessions.
Do not use it for questions about the current environment from inside a running box. Inside the container, use yolobox instead.
- Start from the user's intent, then choose the smallest
yolobox command or flag set that accomplishes it.
- Check
yolobox config when defaults, merged config, or flag precedence matter.
- If
default_harness is set, bare yolobox launches that shortcut; use yolobox shell for an explicit shell.
- Prefer explicit isolation and safety flags:
--scratch for disposable or concurrent sessions that must not share /home/yolo.--readonly-project when the agent only needs read access to the project tree.
