/export-session-as-markdown
Use when the user wants to export a Claude Code session transcript as a readable Markdown file — converts the current session (or a specified transcript path) into GitHub-flavored Markdown with metadata header, collapsible tool results, and thinking blocks
$ npx -y skills add ed3dai/ed3d-plugins --skill export-session-as-markdown --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/export-session-as-markdown
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user wants to export a Claude Code session transcript as a readable Markdown file — converts the current session (or a specified transcript path) into GitHub-flavored Markdown with metadata header, collapsible tool results, and thinking blocks
SKILL.md
export-session-as-markdown.SKILL.mdname: export-session-as-markdown
description: Use when the user wants to export a Claude Code session transcript as a readable Markdown file — converts the current session (or a specified transcript path) into GitHub-flavored Markdown with metadata header, collapsible tool results, and thinking blocks
Export Session as Markdown
Export a Claude Code session transcript to a human-readable GitHub-flavored Markdown file.
Prerequisites
- The `ed3d-session-reflection` plugin must be installed (provides the `reduce-transcript.py` script).
- The current session's transcript path must be available (injected by the SessionStart hook). If it is not available, ask the user for the transcript path.
Invocation
The user may invoke this as:
- `/export-session-as-markdown` — export the current session
- `/export-session-as-markdown /path/to/transcript.jsonl` — export a specific transcript
- `/export-session-as-markdown /path/to/transcript.jsonl /path/to/output.md` — export to a specific output path
Steps
1. Determine the transcript path
If an argument was provided, use it as the transcript path. Otherwise, use the current session's transcript path from the SessionStart hook injection.
If you cannot determine the transcript path, tell the user:
I don't know the current session's transcript path.
Either provide a path: /export-session-as-markdown /path/to/session.jsonl
Or ensure the ed3d-session-reflection SessionStart hook is active.
2. Determine the output path
If a second argument was provided, use it as the output path. Otherwise, default to the current working directory with a descriptive filename:
session-transcript-YYYY-MM-DD.md
If a file with that name already exists, append a counter: `session-transcript-YYYY-MM-DD-2.md`.
3. Export the transcript
Run the script with the `--markdown` flag:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/reduce-transcript.py" "<transcript_path>" "<output_path>" --markdown4. Report the result
Tell the user where the file was written and its size. Example:
Exported session transcript to ./session-transcript-2026-03-20.md (346 KB)
Read more
name: export-session-as-markdown description: Use when the user wants to export a Claude Code session transcript as a readable Markdown file — converts the current session (or a specified transcript path) into GitHub-flavored Markdown with metadata header, collapsible tool results, and thinking blocks
Export Session as Markdown
Export a Claude Code session transcript to a human-readable GitHub-flavored Markdown file.
Prerequisites
- The `ed3d-session-reflection` plugin must be installed (provides the `reduce-transcript.py` script).
- The current session's transcript path must be available (injected by the SessionStart hook). If it is not available, ask the user for the transcript path.
Invocation
The user may invoke this as:
- `/export-session-as-markdown` — export the current session
- `/export-session-as-markdown /path/to/transcript.jsonl` — export a specific transcript
- `/export-session-as-markdown /path/to/transcript.jsonl /path/to/output.md` — export to a specific output path
Steps
1. Determine the transcript path
If an argument was provided, use it as the transcript path. Otherwise, use the current session's transcript path from the SessionStart hook injection.
If you cannot determine the transcript path, tell the user:
I don't know the current session's transcript path. Either provide a path: /export-session-as-markdown /path/to/session.jsonl Or ensure the ed3d-session-reflection SessionStart hook is active.
2. Determine the output path
If a second argument was provided, use it as the output path. Otherwise, default to the current working directory with a descriptive filename:
session-transcript-YYYY-MM-DD.md
If a file with that name already exists, append a counter: `session-transcript-YYYY-MM-DD-2.md`.
3. Export the transcript
Run the script with the `--markdown` flag:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/reduce-transcript.py" "<transcript_path>" "<output_path>" --markdown4. Report the result
Tell the user where the file was written and its size. Example:
Exported session transcript to ./session-transcript-2026-03-20.md (346 KB)
This is my collection of plugins that I use on a day-to-day basis for getting stuff done with Claude Code. Most of these are development-oriented in some way or another, but also often end up being useful for other things.
Repo: ed3dai/ed3d-plugins
Other skills on ed3d-plugins.
- /doing-a-simple-two-stage-fanout
Use when analyzing a large corpus of text, code, or data that exceeds a single agent's effective context - orchestrates parallel Worker subagents, Critic review subagents, and a final Summarizer subagent with task tracking and failure recovery
Open skill - /using-generic-agents
Use to decide what kind of generic agent you should use
Open skill - /creating-a-plugin
Use when creating a new Claude Code plugin or setting up plugin structure - provides complete file organization, manifest format, and component definitions for commands, agents, skills, hooks, and MCP servers
Open skill - /creating-an-agent
Use when creating specialized subagents for Claude Code plugins or the Task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agents
Open skill - /maintaining-a-marketplace
Use when creating, releasing, or maintaining a Claude Code Plugin Marketplace - covers marketplace.json schema, version management, release checklists, changelog conventions, and validation to prevent sync drift between plugin.json and marketplace.json
Open skill - /maintaining-project-context
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
Open skill

