Write a durable session log with completed work, findings, open questions, and next steps. Use when the user asks to log the session, write a lab notebook entry, or record what was done.
Installs into .claude/skills of the current project.
Are you the author of Session Log?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/yichen-zju-session-log)
---
name: session-log
description: Write a durable session log with completed work, findings, open questions, and next steps. Use when the user asks to log the session, write a lab notebook entry, or record what was done.
---
# Session Log
Write a session log for the current research work.
## Requirements
- Summarize what was done in this session.
- Capture the strongest findings or decisions.
- List open questions, unresolved risks, and concrete next steps.
- Reference any important artifacts written to `notes/`, `outputs/`, `experiments/`, or `papers/`.
- If any external claims matter, include direct source URLs.
- Save the log to `notes/` as markdown with a date-oriented filename (e.g. `notes/2026-07-26-<slug>.md`).
- For substantial multi-session work, also append a short entry to `CHANGELOG.md` (the lab notebook): active objective, what changed, verification state, next step.
