share-session

Share Session

Overview

Convert Claude Code sessions into readable markdown format for easy sharing. This skill finds sessions by fuzzy matching todo items and generates well-formatted markdown documents. If this is loaded by user's explicit request but no comments there, just execute followings.

Workflow

Step 1: CRITICAL - Create Todo for Session Identification

MANDATORY: You MUST use TodoWrite tool to create a todo item that describes what this session is about.

IMPORTANT: You do NOT need to know the session ID. Describe the session content instead.

CORRECT Usage:

TodoWrite(todos=[{
    "content": "share this session about ccusage integration and time tracking",
    "status": "in_progress",
    "activeForm": "Sharing session"
}])

Good Examples (describe session topic):

• ✅ "share this session about ccusage integration"
• ✅ "export conversation on implementing time tracking"
• ✅ "share current session with share-session improvements"

Bad Examples (using session ID directly):

• ❌ "get session id of 62d3a2b2-102c-43d3-8414-0a30d7a5e5e0" (you don't know session ID yet!)
• ❌ "export 62d3a2b2" (session ID unknown)

How it works:

1. You create todo with session description
2. Claude Code saves todo as: ~/.claude/todos/{SESSION-ID}.json
3. Script searches todo content using fuzzy matching (60% threshold)
4. Script extracts SESSION-ID from the matching todo filename
5. Script uses that SESSION-ID to find transcript

Why this is required:

• Without a todo, the script has no way to identify which session to export
• The todo file name is the ONLY place where session ID is stored
• Fuzzy matching allows flexible queries ("share this session" matches multiple variations)

Common mistakes:

• ❌ Forgetting to call TodoWrite before running the script
• ❌ Using session ID in todo content (you don't know it yet!)
• ❌ Query in Step 2 doesn't match todo content at all

Step 2: Run share_session.py