share-claude-code-chat
Export Claude Code JSONL conversations into high-fidelity HTML pages with safe collapsible tool timelines, then deploy them as public PreviewShip links.
Documentation
Answer First
The share-claude-code-chat skill is a companion workflow for Claude Code conversations. It reads local Claude Code JSONL history, reconstructs visible user and assistant messages, keeps tool activity in readable collapsible timelines, hides reasoning text and unsafe raw tool outputs, then deploys the generated HTML with PreviewShip so teams can share research trails, implementation records, and review context.
Deploy build artifacts, not source-code zips.
If you upload a zip, build the project first and zip the static output folder such as dist, build, out, or public with index.html and assets. Do not zip raw React/Vue/Next source folders with package.json and node_modules. Single.html,.md/.markdown, and.pdf files are supported directly by console upload, CLI, MCP, and the VS Code/Cursor extension.
Key takeaways
Comparison snapshot
Why Claude Code needs its own sharing skill
Claude Code stores conversation history, message types, tool calls, and intermediate events differently from Codex. Reusing a Codex-specific parser would either miss useful activity or put tool timelines in the wrong place.
The Claude Code skill treats the conversation as a separate source format. It reconstructs user and assistant messages, attaches tool activity to the surrounding assistant turn, and renders the result as a self-contained HTML page that is easier to review than screenshots or pasted terminal output.
FAQ
Is share-claude-code-chat the same as share-codex-chat?
No. They share the same PreviewShip publishing goal, but Claude Code and Codex store different local transcript formats. The Claude Code skill has its own parser and tool-timeline handling.
Does the skill publish Claude Code reasoning?
No. It is designed to hide reasoning text and show only safe, visible conversation content plus summarized tool activity.
Can it show tool calls without overwhelming the page?
Yes. Tool activity is grouped into collapsible timelines so readers can expand the process when they need it and keep the main answer readable.
Does it require a PreviewShip API key?
Yes for deployment. If the CLI is not authenticated, run `npx previewship login` or configure `PREVIEWSHIP_API_KEY` before sharing.