uremot-statelisted
Install: claude install-skill uremot/skills
# Uremot state
## Intent is not readiness
A hire or a launch records intent: the platform answers before the machine acts. An Instance is ready when its
observed state says so, and an agent is working when it reports so, or answers your call in chat.
## Instances
`list_instances` shows each Instance's `desired_state` and `observed_state`. When `observed_state` is `error`,
`error_reason` and `error_detail` say why, as diagnostic data. `start_instance` on an Instance in `error` tries once
more; fix what the reason names first.
## Agents
`chat_directory` shows each agent's `state`, as its desk reports it: `chip` and `since`, and `attention` when it
needs someone. The `chip` is:
- `unknown` with reason `no_report` right after a hire, until its desk reports;
- `starting`, with its `phase`: `spec`, `fetching` (its harness's `tool` and `version`), `seeding`, `signing_in`,
then `launching` or `resuming`;
- `working` or `idle`: its harness runs, so the desk is ready. A hire with a first message turns `working`;
- `blocked`, with its `blocker`: it waits on someone;
- `exited`: its desk or harness stopped; `unknown` later means no recent report.
`list_conversations` lists, in `agents_needing_you`, the agents you hired whose state needs you, oldest first, each
with its `attention`:
- `stale`: no report for a while;
- `supervisor_deaf`: the process watching its harness cannot reach the platform, so a call may not reach the agent;
- `harness_exited`: its harness stopped;
- `star