← ClaudeAtlas

atmos-canvas-agentlisted

Drive the user's open Atmos Canvas via `atmos canvas` CLI: diagrams, layout, screenshots, local .atmos.tldr documents, and (when needed) durable document scripts or one-shot exec. Use for sketch/draw/diagram/layout requests, and for interactive surfaces or clickable UI only when the user asks for that behavior.
AruNi-01/atmos · ★ 3 · Web & Frontend · score 70
Install: claude install-skill AruNi-01/atmos
# Atmos Canvas Agent Skill Operate the **live Atmos Canvas** with `atmos canvas`. Most requests are **static diagrams** — use structured drawing commands only. Load deeper references only when the task needs documents or interactive scripts. ```text Default path: create / layout / lint / screenshot / idle Only if needed: documents CLI · document scripts · exec ``` --- ## Prerequisites 1. `atmos` on `PATH` (`atmos --version`). 2. Canvas open against local Atmos Server. 3. `atmos canvas status` — for **live editor** work: `bridge.accepting_count >= 1` and bridge **enabled** (Canvas Bot). Document-only `docs` / `doc-*` do **not** need the bridge. 4. **Check client capabilities** before `script-*` / `exec`: - Supported: `document-scripts.1` and/or `exec.1` in `bridge.clients[].capabilities` - Stale UI (Desktop static build / old web): often only `canvas.v1` → **do not** call `script-put` / `exec`; tell the user to rebuild/restart Canvas on the APP-037 branch so the bridge advertises script support. Fresh shell per tool call — re-run full commands; do not rely on exported env vars. --- ## Decision tree (load references on demand) | User intent | What to do | Load reference | |-------------|------------|----------------| | Diagram, architecture, cards, labels, arrange | Structured verbs below | *(this file only)* | | List / save-as style file ops / rename boards | `docs` / `doc-*` | [`references/documents.md`](references/documents.md) | | Clickable UI, keyboard surf