export-session

Converts Claude Code session JSONL transcripts into Markdown files with YAML frontmatter.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill export-session-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: export-session
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/social-media-tools/skills/export-session
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill export-session-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Claude Code sessions are stored as raw JSONL transcripts that are hard to read, share, or archive. This Skill converts them into clean, readable Markdown files so conversations can be kept as reference material in a plans directory. ## Core Features & Use Cases - Transcript Conversion: Parses session JSONL files and extracts user and assistant turns, skipping tool results, sidechains, and system reminders. - Automatic Session Resolution: Locates the most recent transcript for the current project, or accepts an explicit JSONL path or session ID. - Structured Output: Writes Markdown files with YAML frontmatter (session-id, date, source, type) and word-boundary-safe titles, named by date, slug, and session ID prefix. - Use Case: After a long planning session, ask to export the session and get a readable Markdown recap saved under your plans directory for later indexing or review. ## Quick Start Ask the assistant to export the most recent session transcript to Markdown, optionally providing a session ID or JSONL file path.

Frequently Asked Questions about export-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export a Claude Code session to Markdown?▼

Ask the assistant to export the session, optionally passing a JSONL path or session ID. The skill runs a bundled script that converts the transcript into a Markdown file under the plans directory's sessions folder.

Where does the session export get saved?▼

Exports are written to the sessions subdirectory of the plansDirectory setting in .claude/settings.json, falling back to docs/plans/sessions if unset. Files are named with the date, a slug from the first user message, and a session ID prefix.

Can I export a session from a different project?▼

By default the skill only exports transcripts for the current project. It will export another project's transcript only if you explicitly point it at that JSONL file or session ID.

What content is included in the exported Markdown?▼

The export includes user and assistant turns only, skipping tool results, sidechains, and system reminders. It adds YAML frontmatter with session-id, date, source, and type fields for later indexing.

Why does the export fail with no conversation turns found?▼

This happens when the JSONL file contains no user or assistant messages after filtering, such as a transcript made only of tool results or system records. Verify the path points to a real session transcript.