
Session Logger
Persist Claude Code (or similar) chat turns into timestamped markdown logs so you can resume work without re-explaining context.
Overview
Session Logger is a journey-wide agent skill that saves the current agent conversation to a timestamped markdown file in `sessions/`—usable whenever a solo builder needs to preserve context before ending a coding session
Install
npx skills add https://github.com/charon-fan/agent-playbook --skill session-loggerWhat is this skill?
- Writes `sessions/YYYY-MM-DD-{topic}.md` from the current conversation
- Activates on bilingual triggers (e.g. 保存对话信息, save session, log session)
- Summarizes decisions, context, and problem-solving steps into a structured log
- Keeps logs local via `.gitignore` so session files are not committed
- Uses Read, Write, Edit, and Bash to create and place session files
- Session files use pattern sessions/YYYY-MM-DD-{topic}.md
- Bilingual trigger table covers four Chinese and four English phrases
Adoption & trust: 617 installs on skills.sh; 58 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finish a long agent session full of decisions and fixes, then start fresh tomorrow with no structured record of what was agreed or tried.
Who is it for?
Claude Code users who hop between sessions on the same repo and want zero-setup conversation archiving.
Skip if: Teams that need searchable team-wide memory, compliance audit trails in git, or automatic logging without an explicit save trigger.
When should I use this skill?
User says 保存对话, 保存对话信息, 记录会话, save session, save conversation, log session, or save this session.
What do I get? / Deliverables
You get a local session markdown log you can reread on the next run so the agent (and you) pick up from documented context instead of repeating discovery.
- Timestamped markdown session log in sessions/
- Structured summary of key decisions and context from the conversation
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
After implementing an API with the agent, save the session so migration choices and edge cases are documented before you switch tasks.
Log a long code-review thread so you can apply the same feedback checklist in a follow-up PR without re-reading chat.
Capture an incident-debugging conversation to compare hypotheses the next time the same alert fires.
Archive a scoping debate with the agent before you commit to a milestone plan.
Save a support-escalation triage session to reuse troubleshooting steps for similar tickets.
How it compares
Use for explicit end-of-session snapshots; use a vector memory skill (e.g. AgentDB patterns) when agents must retrieve facts automatically across many sessions.
Common Questions / FAQ
Who is session-logger for?
Solo and indie builders using Claude Code (or compatible agents) who want markdown session notes on disk without building a custom logging pipeline.
When should I use session-logger?
After meaningful Build or Ship work when you will pause; during Operate debugging marathons before context compacts; at Validate brainstorms you want to revisit; anytime you say save session or 保存对话信息.
Is session-logger safe to install?
It writes files under your project and uses Bash—the playbook gitignores `sessions/`. Review the Security Audits panel on this Prism page and skim allowed-tools before enabling on sensitive repos.
SKILL.md
READMESKILL.md - Session Logger
# Session Logger Automatically saves conversation history to persistent session log files. ## Overview Session Logger captures your conversations with Claude Code so you can: - Reference previous decisions and context - Maintain continuity across sessions - Learn from past problem-solving approaches - Track project evolution ## Installation ```bash mkdir -p ~/.claude/skills ln -s ~/Documents/code/GitHub/agent-playbook/skills/session-logger ~/.claude/skills/session-logger ``` ## Usage Simply say: ``` "保存对话信息" ``` The skill will automatically: 1. Review the conversation 2. Extract key information 3. Create a session log in `sessions/` ## Trigger Phrases | 中文 | English | |------|---------| | 保存对话信息 | save session | | 保存本次对话 | save conversation | | 记录会话内容 | log session | | 保存session | save this session | ## Session File Location ``` sessions/YYYY-MM-DD-{topic}.md ``` ## Privacy Session logs are in `.gitignore` - they are NOT committed to git. --- name: session-logger description: Saves conversation history to session log files. Use when user says "保存对话", "保存对话信息", "记录会话", "save session", or "save conversation". Automatically creates timestamped session log in sessions/ directory. allowed-tools: Read, Write, Edit, Bash --- # Session Logger A skill for automatically saving conversation history to persistent session log files. ## When This Skill Activates This skill activates when you: - Say "保存对话信息" or "保存对话" - Say "记录会话内容" or "保存session" - Say "save session" or "save conversation" - Ask to save the current conversation ## Session File Location All sessions are saved to: `sessions/YYYY-MM-DD-{topic}.md` ## What Gets Logged For each session, log: 1. **Metadata** - Date and duration - Context/working directory - Main topic 2. **Summary** - What was accomplished - Key decisions made - Files created/modified 3. **Actions Taken** - Checklist of completed tasks - Pending follow-ups 4. **Technical Notes** - Important code snippets - Commands used - Solutions found 5. **Open Questions** - Issues to revisit - Follow-up tasks ## Session Template ```markdown # Session: {Topic} **Date**: {YYYY-MM-DD} **Duration**: {approximate} **Context**: {project/directory} ## Summary {What was accomplished in this session} ## Key Decisions 1. {Decision 1} 2. {Decision 2} ## Actions Taken - [x] {Completed action 1} - [x] {Completed action 2} - [ ] {Pending action 3} ## Technical Notes {Important technical details} ## Open Questions / Follow-ups - {Question 1} - {Question 2} ## Related Files - `{file-path}` - {what changed} ``` ## How to Use ### Option 1: Automatic Logging Simply say: ``` "保存对话信息" ``` The skill will: 1. Review the conversation history 2. Extract key information 3. Create/update the session file ### Option 2: With Topic Specify the session topic: ``` "保存对话,主题是 skill-router 创建" ``` ### Option 3: Manual Prompt If auto-extraction misses something, provide details: ``` "保存对话,重点是:1) 创建了 skill-router,2) 修复了 front matter" ``` ## File Naming | Input | Filename | |-------|----------| | "保存对话" | `YYYY-MM-DD-session.md` | | "保存对话,主题是 prd" | `YYYY-MM-DD-prd.md` | | "保存今天的讨论" | `YYYY-MM-DD-discussion.md` | ## Session Log Structure ``` sessions/ ├── README.md # This file ├── 2025-01-11-skill-router.md # Session about skill-router ├── 2025-01-11-prd-planner.md # Session about PRD planner └── 2025-01-12-refactoring.md # Session about refactoring ``` ## Privacy Note Session logs are stored in `sessions/` which is in `.gitignore`. - Logs are NOT committed to git - Logs contain your actual conversation - Safe to include sensitive information ## Quick Reference | You say | Skill does | |---------|------------| | "保存对话信息" | Creates session log with today's date | | "保存今天的对话" | Creates session log | | "保存session" | Creates session log | | "记录会话" | Creates session log | ## Best Practices 1. **Save at key milestones**: After complet