curatorlisted
Install: claude install-skill ourostack/desk
# Curator
Curator has two jobs within authorized maintenance scope: the improvement-card routine and the operator-requested friction backlog pass. Automatic card creation is not authority for an ordinary user-task agent to take the card, launch a child or open a tooling PR. Respect an existing repair owner. Worker remains the agent; curator is its procedure, not a competing controller.
## The improvement-card routine
An improvement card is one file under `_meta/improvement/`, opened by the factory loop or system friction. Establish that tooling maintenance is in this task's authorized scope before taking one; no repeat approval is needed when that scope already exists. `improvement_next` claims the oldest available card and returns its `claim_id` and authority text. It refuses in a noninteractive or headless session. Existing bounds remain: 1 live claim per machine, 2 new claims per machine per day, a claim lasts 4 hours. A refusal (`claim_held`, `cap_reached`, `none_open`) says why; never hunt for card files to work around it.
the authority, in short: decide and fix. a human is asked only for a true gate: money on a human's payment method, a credential or an account only a human can act in, or an irreversible destructive action. every ruling you make while working the card goes in the countermeasure pull request, and the card links to it.
1. **andon first.** an open `andon` issue means a release made a quality measure clearly worse for a plugin the store tracks; its car