st-auditlisted

# ST Audit — Discover & Explain Current Config Read-only audit of SillyTavern configuration. Surfaces what's currently configured, why each knob matters, and what to change for a given goal. **Does NOT modify anything** — feeds context into conversation so user decides next move. **Why this exists:** ST has 100KB+ settings.json + 10+ extensions, each with sub-config. Most users don't know which knobs are load-bearing vs cargo-cult. This skill closes the discovery gap. **Usage:** ``` /st-audit # full sweep, grouped by domain /st-audit <setting-key> # explain one setting (current value + what it does + safe range) /st-audit goal "<natural language>" # goal-driven: list relevant settings + recommendations ``` ## Constants ``` ST_DATA = /home/haint/Projects/home-server/sillytavern/data/default-user SETTINGS = $ST_DATA/settings.json # fallback only; prefer mcp__st__st_get_settings PLAYBOOK = /home/haint/Projects/home-server/sillytavern/PROMPT-PLAYBOOK.md ``` ## Knowledge Source Order 1. `PROMPT-PLAYBOOK.md` — 33 verified gotchas, the canonical local knowledge base. Always cite gotcha number when relevant. 2. **Live settings via `mcp__st__st_get_settings()`** — current state (ground truth). Works while ST runs (no file-lock risk). Falls back to `Read SETTINGS` if MCP unavailable (ST container down). 3. ST source defaults (read from `/home/node/app/public/scripts/extensions/<name>/index.js` via `podman exec` if needed). 4. Built-in skill