tinyhat:open — read from or open the latest audit

tinyhat:open — read from or open the latest audit

Two jobs, decided by what the user actually asked for:

1. Answer a specific question about the last audit — read the persisted JSONs at ${CLAUDE_PLUGIN_DATA}/latest/{snapshot,analysis}.json and reply in chat. No browser.
2. Open the HTML report as-is — when the user just wants to see it.

Never regenerate. That's /tinyhat:audit's job. The agent analysis step is non-trivial and the user may not want to spend the turns.

Where the data lives

Tinyhat writes under ${CLAUDE_PLUGIN_DATA} (the Claude-Code-sanctioned per-plugin data directory). Older installs may still have artefacts under the legacy ~/.claude/tinyhat/ — fall back to it only if the new path is empty. The next write-capable Tinyhat command will migrate the legacy directory forward.

Decide which job you're doing

Read the user's message. If it contains a specific question — "what did the audit say about dormant skills?", "which skills did I use this week?", "remind me what you recommended" — it's job 1: answer from JSON. The phrasing is asking for a fact, not a viewing experience.

If the message is vague-open — "open tinyhat", "show me the report", "/tinyhat:open" — it's job 2: open the HTML.

When in doubt, prefer job 1. Reading from JSON and answering inline keeps the user's attention in the terminal; opening a browser tab moves it away.

Job 1 — answer from JSON

1. Find the latest directory: prefer ${CLAUDE_PLUGIN_DATA}/latest/, fall back to ~/.claude/tinyhat/latest/ only if the first is empty.
2. Check that analysis.json and snapshot.json both exist in that directory.
   • If missing, say "I don't have a saved audit to read from — let me run a fresh one" and hand off to /tinyhat:audit. Stop.
3. Read one or both JSONs with the Read tool. Prefer analysis.json for editorial questions ("what stood out?", "what did you recommend?") and snapshot.json for factual questions ("which skills did I use?", "how many sessions?").
4. Answer in chat. Cite specific numbers/skills from the JSON. Name the date the audit ran (run-stamp.txt). End with one line the user can act on — usually a file:// link to the full HTML if they want more detail.

Shape of a good answer

From your 2026-04-23 audit: 107 of 121 installed skills were dormant — the bulk (82) are plugin-bundled skills that came with marketplaces you installed. Open the full report at file://${CLAUDE_PLUGIN_DATA}/latest/report.html to see them grouped by origin.

Rules

• Never re-run gather_snapshot.py. The JSONs on disk are the source of truth for this skill.
• Use literal numbers from the JSON. Don't paraphrase counts.
• Only reference skills that appear in snapshot.inventory.
• If the question can't be answered from the JSON (e.g. "what would you recommend next week?"), say so and suggest running a fresh audit.

Job 2 — open the HTML

1. Check whether ${CLAUDE_PLUGIN_DATA}/latest/report.html exists.
   • If it does, use it.
   • If it doesn't, check ~/.claude/tinyhat/latest/report.html.
   • If neither exists, tell the user "No skill-audit report yet — let me create your first one" and hand off to /tinyhat:audit. Stop here; don't try to open nothing.
2. Open the file with the platform-appropriate command:

open "${CLAUDE_PLUGIN_DATA}/latest/report.html"        # macOS
xdg-open "${CLAUDE_PLUGIN_DATA}/latest/report.html"    # Linux
start "${CLAUDE_PLUGIN_DATA}/latest/report.html"       # Windows

If unsure which OS, use Python's webbrowser module (cross-platform). Pass the scripts dir as argv so the helper imports from the same bundled tinyhat_paths as the rest of the plugin:

python3 -c 'import sys, webbrowser; sys.path.insert(0, sys.argv[1]); from tinyhat_paths import default_home_root; webbrowser.open((default_home_root() / "latest" / "report.html").as_uri())' "${CLAUDE_SKILL_DIR}/../../scripts"

3. In one short sentence, tell the user what they're looking at — the date from ${CLAUDE_PLUGIN_DATA}/latest/run-stamp.txt is enough: "Opened your most recent skill-audit report from 2026-04-23. Use /tinyhat:audit to refresh."