5dive-clilisted

# 5dive-cli This skill teaches you to drive the `5dive` command on a 5dive runtime VM. You are running inside one such VM. You can spawn additional agents on the same host by shelling out to `sudo 5dive ...` and parsing the JSON envelope it emits when you pass `--json`. ## When to use this skill Use it whenever the work in front of you would benefit from a second pair of hands — for example: - The user asks for a "worker", "sub-agent", "another agent", or "side task". - **The user names a specific sibling agent** — "redirect to marketing", "ask scout", "ping ops", "tell research", "coordinate with X", "hand off to X". First confirm the agent exists via `sudo 5dive agent list --json`, then `agent send` (and pass chat context if the request came from a channel — see "Delegating a request that came in over a channel" below). - A long task could fan out into independent pieces (e.g. audit each route in parallel, run a different model on the same prompt, A/B two implementations). - You need to keep one agent on a hot context while a second one investigates something orthogonal. - The user wants to inspect / restart / pair / tear down an agent that already exists on the host. - You need a machine-readable health check of the host's coding-CLI stack. - You're coordinating work across several agents and want a shared to-do list or a reporting structure (`5dive task`, `5dive org`). - Work should recur on a schedule (`task add --recurring`) or an agent should be w