operator-auditlisted

# Operator Audit ## The Job Look at what the user actually did with their AI over the last one to two weeks, then tell them the five things most worth doing next. Not generic productivity advice: five recommendations grounded in their own projects, their own unfinished threads, and their own repeated work. ## Privacy First, Said Out Loud Before reading anything, ask: "To build this audit, I need to read your recent Claude Code or Codex conversation history on this machine for the audit window. Everything stays here and nothing is sent anywhere. Do you approve this history access?" Wait for an explicit yes. Silence, an unrelated reply, or the original audit request does not count as approval. Do not list, open, search, or inspect any history file before approval. If the user declines, offer the spoken mini-audit instead. This skill must never quote sensitive content (credentials, client names in delicate contexts) back into the audit without need; summarize themes, not secrets. ## Step 1: Find the History Only after explicit approval, locate this client's local conversation history and take the files modified in the last 7 to 14 days (ask which window they want; default 14): - **Claude Code:** session transcripts under `~/.claude/projects/` (one folder per project, `.jsonl` files; the folder names indicate the project paths). - **Codex:** session files under `~/.codex/sessions/` and `~/.codex/archived_sessions/`. - If both exist, ask whether to audit just this client o