Automated summary
Writes a detailed session log entry into the Claude Code project memory file, capturing goals, decisions, code changes and next steps.
Strengths
- Very thorough enforced structure: summary, decisions, files touched, dead ends, project state and next steps
- Handles an `## Active Goals` section by archiving goals with final status and then removing it
- Rotates the file so only the 8 most recent entries are kept
- Includes a step to persist durable decisions into topic memory files
Limitations
- Tightly coupled to Claude Code's ~/.claude/projects/<project-path>/memory/ layout
- Output quality relies entirely on the model's own review of the conversation, with no automated verification
- Only 8 entries survive: older history is permanently dropped
At the end of a substantial working session when context continuity for next time matters.
For a short or purely exploratory exchange that doesn't warrant being archived in project memory.
Security analysis
CautionThe skill performs no execution, network, or credential-handling actions; its only effect is reading the conversation and writing/editing a markdown file in the user's home directory. That is a legitimate and common memory-management pattern, but it does persist potentially sensitive conversation content to plaintext and destructively rewrites an existing file (removing the Active Goals block and oldest entries) without a backup or confirmation step, which warrants a caution rating rather than safe.
- •Writes and rewrites files outside the project workspace, in the user's home directory (~/.claude/projects/<project-path>/memory/session_log.md), with no declared allowed-tools or scope limits
- •Persists full conversation contents ('Review the full conversation... messages, tool calls, decisions') to a plaintext file on disk, which can silently capture secrets, tokens, or sensitive business context discussed in-session
- •Performs destructive in-place edits on a pre-existing file: it REMOVEs the '## Active Goals' section and truncates older entries past 8 — a mis-parse could lose user data with no backup step
- •Assumes a project-path slug convention but gives no canonical mapping rule, so writes could land in an unintended memory directory
- •No network calls, shell commands, credential access, or obfuscated payloads — risk is limited to filesystem persistence
Examples
Write a session log entry for what we just did in this conversation.Log this session and close out the Active Goals section at the top of session_log.md with their final status.Create a session log entry now, and also save the architectural decisions we made into the relevant topic memory files.Write a detailed session log entry for the current conversation.
Instructions
- Determine the project memory path. Based on the current working directory, find or create the corresponding
~/.claude/projects/<project-path>/memory/folder. If asession_log.mdfile doesn't exist there, create one with this frontmatter:
---
name: session_log
description: detailed rolling session recaps with full context for project continuity
type: project
---
-
Check for active goals. Look for an
## Active Goalssection at the top ofsession_log.md(between frontmatter and dated entries). If it exists, include those goals with final status in the log entry. After writing the entry, REMOVE the## Active Goalssection from the top of the file (the goals are now archived inside the dated entry). -
Review the full conversation. Go through everything discussed in this session -- messages, tool calls, decisions, code changes, dead ends, blockers.
-
Write a new entry at the TOP of the file (below the frontmatter, above any existing entries — and above any Active Goals section, which you're about to remove anyway) using this exact format:
## YYYY-MM-DD -- [short descriptive title]
**Summary:**
2-3 sentence paragraph describing what this session was about, the goal,
and the outcome. Write it so someone with zero context can understand.
**Session goals:** *(include only if Active Goals section existed)*
- [x] Completed goal
- [~] Partially completed goal — what's left
- [ ] Not started goal
- [!] Blocked goal — reason
**What we worked on:**
- Detailed list of activities, not just "did X" but what specifically
- Include context on why each thing was done
**Key decisions & reasoning:**
- Decision made -- why we chose this over alternatives
**Code changes made:**
- List of concrete changes that shipped (or "none -- planning only")
**Files touched:**
- file/paths/here.ts
- (or "none")
**Blockers / Open questions:**
- Unresolved stuff that needs attention next time
**What didn't work / Dead ends:**
- Approaches we tried and abandoned, so we don't retry them
**Dependencies & external context:**
- Links to other systems, APIs, services, PRs, issues relevant to this work
**Current project state:**
Honest snapshot of where the project stands right now after this session.
**Next steps (prioritized):**
1. Most important thing to do next
2. Second priority
3. Third priority
**Mood / momentum:**
One line -- are we stuck, cruising, exploring, blocked, ready to ship, etc.
-
Rotate old entries. If there are more than 8 entries in the file, remove the oldest ones (at the bottom) to keep only the 8 most recent.
-
Update topic memories if needed. If any key decisions from this session should be permanent knowledge (not session-specific), also save or update the relevant topic memory files.
-
Confirm when done. Tell me what you logged and how many entries are in the file now.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/write-session-log-entry-ms2s7c5m/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/write-session-log-entry-ms2s7c5m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/write-session-log-entry-ms2s7c5m/download' --output '.skill-downloads/write-session-log-entry-ms2s7c5m/SKILL.md.part' && mv '.skill-downloads/write-session-log-entry-ms2s7c5m/SKILL.md.part' '.skill-downloads/write-session-log-entry-ms2s7c5m/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/write-session-log-entry-ms2s7c5m/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
PDF Reader
Productivity
Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.
Discord Messaging Workflows
Productivity
Use the message tool to send, edit, and moderate Discord messages with interactive components.
Interactive Verdict Preview
Productivity
Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.