Skip to content
Skills Library
Documents & office · Conversion & formats

sessionlog:export

/sessionlog:export

This skill should be used when the user asks to "export session log", "convert session to json", "export conversation", "save session", "sessionlog export", "export this session", or wants to export the current Claude Code session as a standard LLM conversation JSON file and human-readable TXT transcript.

Repository
claude-code ↗
Licence
MIT
Last repository change
07.10.2026

Assessment and security

90/ 100Class: good
Format15 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

This skill should be used when the user asks to "export session log", "convert session to json", "export conversation", "save session", "sessionlog export", "export this session", or wants to export the current Claude Code session as a standard LLM conversation JSON file and human-readable TXT transcript.

Triggers from the description

export session logconvert session to jsonexport conversationsave sessionsessionlog exportexport this session
Original author description

This skill should be used when the user asks to "export session log", "convert session to json", "export conversation", "save session", "sessionlog export", "export this session", or wants to export the current Claude Code session as a standard LLM conversation JSON file and human-readable TXT transcript.

How it works

  1. Steps
  2. Output Format
Original SKILL.md headings · 61 lines, 186 words
SKILL.md preview
---
name: sessionlog:export
description: >
  This skill should be used when the user asks to "export session log",
  "convert session to json", "export conversation", "save session",
  "sessionlog export", "export this session", or wants to export the
  current Claude Code session as a standard LLM conversation JSON file
  and human-readable TXT transcript.
disable-model-invocation: false
---

# Session Log Export

Export the current Claude Code session to standard LLM conversation JSON and a human-readable TXT transcript.

## Steps

### 1. Identify current session

Run the following to find the session file:

```bash
project_dir="$HOME/.claude/projects/$(pwd | sed 's|/|-|g')"
current_session=$(ls -t "$project_dir"/*.jsonl 2>/dev/null | head -1)
session_id=$(basename "$current_session" .jsonl)
echo "Session: $session_id"
echo "Source: $current_session"
```

### 2. Determine output directory

Use the output directory specified in the user's prompt. If none was specified, default to `docs/sessionlogs/` relative to the current working directory.

### 3. Run the export script

```bash
"${CLAUDE_PLUGIN_ROOT}/scripts/export-session.sh" "$current_session" "<output-dir>" "$session_id"
```

The script produces two files:
- `<output-dir>/claude-<session-id>.json` — standard LLM conversation JSON (array of `{role, content}` objects)
- `<output-dir>/claude-<session-id>.txt` — human-readable transcript with `[user]`/`[assistant]` prefixes

### 4. Report results

Show the user:
- The two output file paths
- Number of messages exported
- File sizes

## Output Format

**JSON** — Array of message objects following the standard LLM conversation format:

```json
[
  {"role": "user", "content": "Hello"},
  {"role": "assistant", "content": [{"type": "text", "text": "Hi there!"}]}
]
```

**TXT** — Human-readable transcript:

```
Session: <session-id>

[user] Hello

[assistant] Hi there!
```

Versions

The database has no other skills named sessionlog:export.

Database snapshot: 13.11.2026 · package version 30c9516314a2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90sessionlog:export-all
    This skill should be used when the user asks to "export all sessions", "export all session logs", "batch export sessions", "sessionlog export-all", "convert all sessions", or wants to export every Claude Code session for the current project as standard LLM conversation JSON and TXT files.
  • 90sessionlog:info
    This skill should be used when the user asks to "show session info", "find session log", "where are session logs", "current session id", "session path", "sessionlog info", or wants to identify the current Claude Code session and its log file location on disk.
  • 90share-transcript:share
    This skill should be used when the user asks to "share a transcript", "export a session", "convert a transcript", "share this conversation", "create a shareable transcript", "export to HTML", "export to markdown", or mentions sharing Claude Code sessions with others.
  • 100session-log
    Append a timestamped changelog entry to the per-project SESSIONLOG.md summarizing what was done in the current session. Use when user says "session log", "log session", "update session log", "write changelog", or at the end of a productive session before exiting. TRIGGER: When…
  • 100chat-export
    Export chat transcripts or conversation JSON into clean Markdown, JSON, or plain-text artifacts. Use this skill when a user wants a reusable export of a chat thread, needs a deterministic transcript cleanup, or wants a conversation converted into a file-oriented format for…
  • 100report
    Export the current reply or card as a standalone styled HTML report in the readable template. Use ONLY when the user asks to save, export or extend THE CURRENT card («همین کارت رو ذخیره کن», "save this card"). Never on a generic "write a report".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.