statslisted

Query or render the state of the scattered kit/tide/tg-cleanup/learned ledgers (the dwarves-kit gate/proof/telemetry corpus, tide file-move state, tg-cleanup snapshots, the learning ledger), and detect + propose backlog rows off anomalies in that state. Use when the operator asks to SEE ledger state -- "show me the ledger state", "my debt", "understanding debt", "telemetry", "token cost" / "how much am I spending on tokens", "kit runs" / "kit lane telemetry", "ledger status", "render the ledger", "ledger dashboard", "share this as an artifact" (mid-ledger-conversation) -- or to check/propose off it -- "any ledger anomalies", "is my debt over threshold", "propose a backlog row from the ledger state". Drives the read-only `stats` CLI (dwarves-kit/lib/stats) and renders the result as EITHER an in-terminal reply (bot-reply-formatting , tables + bar-fills) or a shareable web Artifact, both from the same one query; `stats anomalies` is the feedback-loop path, PROPOSE-only (stages a cc-backlog candidate, never files
dwarvesf/dwarves-kit · ★ 7 · Code & Development · score 75

Install: claude install-skill dwarvesf/dwarves-kit

# stats Read-only, agent-callable observability over the ledgers dwarves-kit and its neighbors (tide, tg-cleanup, learned-ledger) already write. The tool dir is `~/workspace/<owner>/dwarves-kit/lib/stats` (run `uv run stats <cmd>` there). **Everything is read-only: the CLI never writes back to a source ledger; there is no path through this skill that mutates anything.** ## One data path: always query via the `stats` CLI Never re-derive a ledger reading by grepping `~/.local/state/dwarves-kit/logs/` or `tide`'s sqlite or `tg-cleanup`'s json yourself , that is a second, divergent data source and breaks the whole point of the lens (SG-02 already reuses `lane-telemetry` for the kit read; re-implementing it here would drift). Always go through `stats`. ## Which command answers which question | The operator wants | Command | |---|---| | "show me the ledger state" / "kit runs" / "kit lane telemetry" | `stats render kit_runs --surface terminal` | | "my debt" / "understanding debt" | `stats anomalies` (checks `SUM(kit_runs.gates_ovr)` against threshold; this is the current debt signal, superseding a raw grep over `\| DEBT \|` lines). For the raw numbers behind it, `stats query "SELECT rid, gates_ovr FROM kit_runs WHERE gates_ovr > 0" --surface terminal` | | "any ledger anomalies" / "should I propose anything" | `stats anomalies` (report only) or `stats anomalies --propose` (stage a candidate row per fired anomaly into the cc-backlog staging buffer; never files a board row) | | "t