usage-insightlisted

# Usage insight from the statusline state dir claude-code-statusline maintains a read-only-for-you state dir and documents it as a contract (docs/api/state-dir.md in https://github.com/thevibeworks/claude-code-statusline). This skill teaches you to read it and answer usage questions conversationally — the deep-dive version of what the advisor row says in one sentence. ## Ground rules 1. READ-ONLY. Never write, touch, or delete anything under `~/.claude/statusline/`. The statusline is the only writer. 2. Account scoping: state for tagged accounts lives under `~/.claude/statusline/accounts/<tag>/`; the top level is the default account. If `STATUSLINE_ACCOUNT` or `DEVA_AUTH_TAG` is set in the environment, that names the current account. 3. Staleness: trust `fetched_at` (epoch seconds) in usage.cache. Older than ~1h means no active session feeds that account — say the numbers are stale instead of presenting them as now. 4. These files hold account PII (email, uuid, org). Quote numbers and reset times to the user; do not echo emails/uuids unless asked. ## What to read for which question | Question | Source | |----------|--------| | "Why is the line yellow/red?" / "what's my quota now?" | `usage.cache`: `five_hour.{utilization,resets_at}`, `seven_day.*`, `limits[]` (per-model weekly caps, `kind=weekly_scoped`) | | "Should I start a heavy task now?" | `usage.cache` now + `forecast.cache` patterns (below) | | "Which account has headroom?" | every `accounts/*