export-log

Export Claude conversation logs to markdown with metadata.

9|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/ivy/dotfiles --skill export-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-log
Source: https://github.com/ivy/dotfiles/tree/main/home/dot_claude/skills/export-log
Command: npx skills add https://github.com/ivy/dotfiles --skill export-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Export Claude conversation logs to markdown for easy archiving, sharing, and analysis.

Core Features & Use Cases

  • Export current session logs to a readable markdown document.
  • Support batch exports and inclusion of metadata such as timestamps and IDs.
  • Use cases include auditing conversations, generating knowledge snippets, and creating documentation.

Quick Start

Run claude-extract to export the current session log to markdown.

Frequently Asked Questions about export-log

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

FAQPage Schema
How do I export Claude conversation logs to markdown for documentation?

Yes, batch exporting Claude session logs to markdown is supported. The claude-extract tool processes multiple historical or ongoing sessions across Claude environments to generate metadata-rich markdown files for archiving and auditing.

What is the best way to create an audit trail from Claude chat sessions?

Creating an audit trail from Claude chat sessions involves exporting the conversation logs to markdown. This generates metadata-rich files containing timestamps and session IDs, providing a portable record for compliance and review.

Do I need claude-extract to export session logs, or are there other dependencies?

Yes, you need claude-extract and standard CLI tools to locate Claude sessions and generate markdown output. These dependencies are required to locate ongoing or historical sessions across Claude environments for export.

Can I include metadata like timestamps and IDs when exporting Claude logs?

Yes, exporting Claude logs to markdown supports the inclusion of metadata such as timestamps and session IDs. This ensures the generated documentation and audit trails are detailed and traceable across batch exports.

Does exporting Claude logs to markdown work for historical sessions across different environments?

Exporting Claude logs to markdown supports both ongoing and historical sessions across Claude environments. The claude-extract tool locates these sessions and generates readable markdown output for archiving and analysis.