insights-deck

# Insights Deck Skill > Archive a Claude Code insights HTML export and generate a Beamer presentation summarising the findings. All outputs go to `log/insights/` with date stamps. ## When to Use - After exporting the built-in Claude Code insights report - When you want a shareable deck summarising how you use Claude Code - For periodic self-reflection on AI-assisted workflow ## Scope This skill produces **two outputs only**: an archived HTML report and a Beamer deck. Do NOT use insights suggestions to create plans, rules, CLAUDE.md edits, or other follow-up actions during this skill's execution. If the user wants to act on suggestions, that happens after the deck is delivered — as a separate conversation. --- ## Phase 1 — Generate & Archive Insights ### Step 1: Obtain the exported HTML The insights export is produced by a built-in Claude Code command and cannot be generated by Codex. If no HTML path was provided, tell the user: > Please export the Claude Code insights report, then provide the generated HTML path. I can build the archive and deck from either client. If an HTML path was supplied, continue directly. Do not require the active client itself to be Claude Code. ### Step 2: Locate the generated HTML After the export completes, find the most recent insights HTML file: ```bash ls -t /tmp/claude-insights-*.html 2>/dev/null | head -1 ``` If not found in `/tmp/`, check the user's home directory and common download locations. Ask the user for the path if it ...