Read Claude Web Conversation
Reads or exports the COMPLETE transcript of a Claude.ai web conversation, private...
Install
npx skills add daymade/claude-code-skills --skill read-claude-web-conversation -g -a claude-code -y- Repository
- daymade/claude-code-skills1.5k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Reads or exports the COMPLETE transcript of a Claude.ai web conversation, private /chat/... and public /share/... links, via Claude.ai's internal API in the user's logged-in Chrome, plus its files. Use when the user pastes a claude.ai link and asks to read, summarize, export, archive, or extract it, "读这个对话", "导出网页版对话", "拉到本地". Local sessions: read-claude-code-history; exported files: claude-export-txt-better.
Read Claude.ai Web Conversation
Pull a Claude.ai web conversation into a full, structured transcript, every message and every tool call, not just what is currently on screen.
Verified against Claude.ai's web API as of July 2026. These are the same private JSON endpoints the Claude.ai front-end calls; they are not a documented or version-stable public API, so if a request 404s, re-derive the shape from the Network tab (see references/claude-web-api-extraction.md).
This skill vs. its siblings
Pick by the source you are holding, not by the word "conversation":
| Source | Use |
|---|---|
A live claude.ai/chat/… or claude.ai/share/… URL | This skill |
Local Claude Code sessions (~/.claude/projects/*.jsonl) | read-claude-code-history |
An already-exported .txt / .json conversation file | claude-export-txt-better |
Why the obvious approaches fail (read this first)
Four traps, and every one of them fails silently, you get back something that looks like a complete export, and you only notice the loss if you happen to know how long the conversation really was. Assume you are being lied to by default; the fidelity gate in Step 4 exists to make the lies audible.
