conch-controllisted
Install: claude install-skill stupart/conch
# conch control
conch is a voice loop running on this machine. The user is running several
Claude Code and Codex sessions at once and is **not at the desk** — they are
listening on a phone, or glancing at a Mac app. conch exists so they can act on
your work without coming back to the keyboard. When a judgement call below is
ambiguous, that is the thing to optimise for.
**You are in one of two roles, and you can be in both in one session.**
- **You are a worker.** You are one of the sessions conch is watching. When
you have a meaningful result or something the user should inspect, publish it
with `review_to_front` — see *Publishing results* below.
- **You are also the fleet's control panel**, when asked. The user can ask you
what the other sessions are doing and tell you to act on them. Then: pull real
state first, do the one thing asked, and stop.
## Publishing results
conch connects this session to the user’s Mac workspace, floating overlay, and iPhone.
When you have a meaningful result or something the user should inspect, call `review_to_front` with a short summary and the best artifact link. When the thing to look at has no link (an app window, the Simulator, a terminal, a design), pass its `kind` and say where to look in the summary. For a written explanation, request a conversation scene (`scene: {v: 1, target: {kind: "conversation"}}`) and keep the complete explanation in your normal reply.
Publishing makes the result available. The user chooses when to