atmos-clilisted

Operate Atmos product state via the `atmos` CLI (projects, workspaces, terminals, runs, settings, git, headless control). Use when the agent must create or manage Atmos resources without the UI. Do not use for desktop GUI capture/click (atmos-desktop-use), in-page browser DOM (atmos-browser-use), canvas drawing (atmos-canvas-agent), or Device Preview phone (atmos-device-preview).
AruNi-01/atmos · ★ 6 · Web & Frontend · score 72

Install: claude install-skill AruNi-01/atmos

# Atmos CLI (product control) Control Atmos **product state** with the `atmos` binary. Prefer **typed L1 resource commands**. Use `atmos call` only as an escape hatch when no L1 verb exists. ```text Default path: status → project/workspace L1 → terminal/run → settings Escape hatch: atmos call <wire_action> --data '{…}' Not this skill: canvas · desktop-use · browser-use Not this skill: Device Preview phone → `atmos-device-preview`. ``` --- ## Prerequisites 1. `atmos` on `PATH` (`atmos --version`). 2. Atmos Server up (`atmos runtime ensure` or Desktop). 3. Auth when required: `--api-token` / `ATMOS_API_TOKEN` / `ATMOS_LOCAL_TOKEN`. 4. Fresh shell per tool call — re-run full commands. --- ## Envelope (always JSON) Every command prints **one JSON object** to stdout: | Field | Meaning | |-------|---------| | `ok` | success | | `command` | what ran | | `result` | payload when `ok` | | `error.code` / `error.message` | when failed | | `fix` | plain-language recovery | | `next_actions` | suggested next commands (templates + params) | Exit code `0` iff `ok: true`. Prefer following `next_actions` and `fix`. Details: [`references/envelope.md`](references/envelope.md). --- ## Decision tree (load references on demand) | Intent | Commands | Load reference | |--------|----------|----------------| | Server ready? | `atmos status` | [`auth-and-runtime.md`](references/auth-and-runtime.md) | | Auth / start server | `atmos runtime ensure` | [`auth-and-runtime.md`](references/auth-