// 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
ALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.
Use when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency pinning, and module organization
Use when the user wants to review their recent Claude Code sessions for patterns — analyzes the last N sessions (default 5) in the current project, dispatching parallel reviewers per session, then synthesizing cross-session findings
Use when the user wants to review a Claude Code session for quality — analyzes the current session (or a specified transcript path) for prompting effectiveness, agent performance, and environment gaps, producing actionable recommendations
Use when writing skills, CLAUDE.md files, agent prompts, or any directives that involve shell commands, environment variables, API credentials, file creation, or git operations - prevents secrets leakage into LLM context, unsafe shell patterns, and credential exposure
Use when writing instructions that guide Claude behavior - skills, CLAUDE.md files, agent prompts, system prompts. Covers token efficiency, compliance techniques, and discovery optimization.
| 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 a Claude Code session transcript to a human-readable GitHub-flavored Markdown file.
ed3d-session-reflection plugin must be installed (provides the reduce-transcript.py script).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 pathIf 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.
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.
Run the script with the --markdown flag:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/reduce-transcript.py" "<transcript_path>" "<output_path>" --markdown
Tell the user where the file was written and its size. Example:
Exported session transcript to ./session-transcript-2026-03-20.md (346 KB)