← ClaudeAtlas

dashclaw-platform-intelligencelisted

DashClaw platform expert for integration, troubleshooting, and governance. Snapshot-based — prefer live queries via `python -m livingcode query`, or `GET {baseUrl}/api/doctor` when Python/livingcode/the repo are unavailable.
ucsandman/DashClaw · ★ 284 · AI & Automation · score 88
Install: claude install-skill ucsandman/DashClaw
# DashClaw Platform Intelligence **Shape snapshot:** `sha1:72875f6354decf0027708bab99f46777ee68c5b8` **This file is auto-generated.** Do not edit by hand — regenerate with: ```bash python -m livingcode emit skill --output <path-to-SKILL.md> ``` ## Prefer Live Queries The facts below are a snapshot. Before answering any question about DashClaw's current structure, routes, env vars, or schema — run a live query: ```bash python -m livingcode query summary # High-level shape python -m livingcode query routes # Current API surface python -m livingcode query env # Current env vars python -m livingcode query tables # Current schema python -m livingcode query all --json # Full machine-readable shape ``` If the snapshot below disagrees with a live query, **trust the live query**. ### Fallback: no Python, livingcode, or repo checkout `python -m livingcode` only works where the livingcode package and the repo checkout are present (e.g. a developer machine). In OpenClaw / the Claude app neither exists. When you cannot run the queries above, fall back **in this order**: 1. **`GET {baseUrl}/api/doctor`** — live route/shape health straight from the running instance. Requires the workspace API key (`x-api-key: <key>`); returns 401/403 without it. This is the authoritative live source when the CLI is unavailable. 2. **Read the committed static shape** if a repo checkout is reachable: `app/lib/doctor/generated/shape.json` (full machine-readable shape) a