From session-recorder
Records the complete session content and logs it to a daily work directory with a dynamic filename based on the active CLI agent. Use this for automated progress tracking and documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/session-recorder:session-recorderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill enables an AI agent to keep a precise log of its interactions. It records the full history of questions and answers into a date-organized directory structure.
This skill enables an AI agent to keep a precise log of its interactions. It records the full history of questions and answers into a date-organized directory structure.
scripts/record_session.py script to append the content to a file named {$cli-name}-session.md.~/daily_work (automatically expands to user's home directory).Run the following command, replacing <cli-name> with your actual identity:
python scripts/record_session.py "<cli-name>" "<one_sentence_title>" "<full_unedited_session_content>"
If the active agent is Codex and the session is about a bug fix:
npx claudepluginhub primatrix/skills --plugin session-recorderSaves the current Claude Code session transcript as clean markdown (conversation only) and raw transcript files for reuse in memos, blog drafts, or articles. Supports starting, refreshing, and finalizing logs per session.
Logs accomplishments from Claude Code sessions to dated markdown files at session end, context checkpoints, self-improve triggers, or user request.
Generates and saves Markdown session logs capturing objectives, file changes, referenced materials, technical notes, future plans, open items, and metrics to resume project work across conversations.