uremot-onboardlisted
Install: claude install-skill uremot/skills
# Uremot onboarding
This skill turns the repository you are in into a Uremot App: a desktop image built `FROM` UremotOS with the
project's toolchains in it, plus the instructions an agent reads inside it. It writes
three files and drives only the `uremot` command, reading its `--json` output and never its prose:
- `Dockerfile`, single-stage, `FROM registry.uremot.com/uremot/uremot-os:<version>`;
- `Dockerfile.dockerignore`, beside it, so no secret in the repository reaches the image;
- `UREMOT.md`, what an agent working in an Instance of the App needs to know.
The image adds no harness and no `uremot` of its own: a hired agent's desk downloads its harness (Claude Code,
Codex or OpenCode) and herdr from their vendors at each start, verified and cached, `gh` and `glab` at first use,
and runs `uremot` from its Compute, or UremotOS's copy. So the person picks no harness here.
**MIN_UREMOT_VERSION: 0.14.0**, the first `uremot` with `publish --json` and `publish --platform`.
Paths to this skill's own files (`references/`, `assets/`) are relative to its root, the directory that holds this
`SKILL.md`. Read a reference when its step comes, not before. Reading this through `uremot guide` shows only this
file: install the skill first (`uremot skills install --harness <yours>`, or `--dir <directory>`) so the rest is on
disk.
The steps run in order: Check, Scan, Interview, Write, Build and publish. Rebuild is the same flow over files this
skill wrote before. Writing the files needs