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 ### Arguments - `$0` — `[session-id-or-path]`: the session id, or a full path to the `.jsonl`. Strongly recommended — see the fallback under "Locating the session file" when it is missing (the placeholder stays as literal `$0`). - `$1` — `[topic]`: kebab-case topic for `meetings/{YYYY-MM-DD}_{topic}.md`. Optional — when no second argument is passed the placeholder stays as literal `$1`; derive the topic from the session's dominant subject instead. ### Locating the session file - Default location: `~/.claude/projects/<encoded-project-path>/<sessionId>.jsonl` — don't compute `<encoded-project-path>` (the encoding rule is unofficial and unverified for every character); locate the file by id instead: `ls ~/.claude/projects/*/<sessionId>.jsonl`. - `<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 — so the **invoker** should run `echo $CLAUDE_CODE_SESSION_ID` before dispatching (set automatically in Bash tool subprocesses) and pass the result as `[session-id-or-pat...