session-to-meeting-log

# Session → Meeting Log ## When to invoke - The user says "turn this session into a meeting log" or "archive today's discussion". - The session is approaching the context limit and needs a written artifact. - The user mentions "extract notes from `~/.claude/projects/.../*.jsonl`". - A long, multi-turn discussion is wrapping up before switching sessions. ## Inputs ### Locating the session file - Default location: `~/.claude/projects/<encoded-project-path>/<sessionId>.jsonl` - `<encoded-project-path>`: replace every `/` and `.` in the absolute path with `-`, e.g. `/Users/alice/GitHub/MyOrg/my-project` → `-Users-alice-GitHub-MyOrg-my-project`, and `/Users/alice/.claude-mem/observer-sessions` → `-Users-alice--claude-mem-observer-sessions`. - `<sessionId>`: a UUID-like string, passed as the first argument. `context: fork` runs this skill in a subagent with no conversation history and no way to ask the user to confirm a guess — the **invoker** (not this fork) must run `echo $CLAUDE_CODE_SESSION_ID` before dispatching (set automatically in Bash tool subprocesses) and pass the result as `[session-id-or-path]`. If the argument is missing, fail immediately and print this instruction rather than guessing from directory mtime. ### JSONL structure One JSON event per line; common `type` fields: | type | Content | |---|---| | `user` | User prompt, **or** a tool-execution result — a tool result is a `user` line whose `message.content[]` contains a `{type: "tool_result", …}`...