What problem does it solve? Chat and terminal output are poor mediums for proving a change works, walking through code, or reviewing a subsystem visually. This Skill turns verification results, diffs, media, logs, and sourced facts into a polished local HTML portfolio or deck with clear evidence status and provenance. ## Core Features & Use Cases - Evidence decks with explicit status: Classify output as verification, review, code-walkthrough, UI/CLI demo, docs, understanding, or mixed, with statuses like PASS, FAIL, INCOMPLETE, NOT SHOWN, and NEEDS CAPTURE so missing evidence is never hidden. - Structured portable document model: Produces index.html, show-me.json, manifest.json, copied media assets, and command logs with provenance (branch, commit, timestamps, exit codes, redactions). - Optional Lavish visual routing: After the canonical deck is rendered, it can route to a Lavish visual surface per repo config (suggest/prompt/auto) with non-fatal fallbacks; the portable deck always remains canonical. - Use Case: After implementing a feature, ask for a proof deck: the Skill gathers test logs, screenshots, and diffs, then renders a dark-styled HTML report showing exactly what passed, what failed, and what still needs capture. ## Quick Start Ask the agent to create a show-me evidence deck proving the current branch's changes work, including test output and screenshots.