How do I install the Save Diary skill?

Run npx skillmds@latest add lethilu4796/save-diary in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Save Diary safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Save Diary?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Save Diary free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Save Diary?

lethilu4796 (@lethilu4796) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Save Diary by lethilu4796 — Agent Skill

Name: Save Diary
Author: lethilu4796

Save Diary

MUST use when user says 'save diary', 'write diary', 'diary entry', 'update diary', or 'document session'. Also auto-trigger at the end of any significant session (feature shipped, major bug fixed, architecture decision, new project started).

lethilu4796 6b5f2d7 3.3 KB Updated Sep 17, 2026

File contents

Dev Diary — Session Documentation Skill

Today's story takes shape.

Activation

When this skill activates, output: "Dev Diary — documenting today's session."

Context Guard

Context	Status
User says "save diary" / "write diary" / "diary entry"	ACTIVE — full diary write
End of significant session	ACTIVE — auto-document
User says "review diary"	ACTIVE — read recent entries
Mid-conversation (no save request)	DORMANT — no diary action

Protocol

Step 1: Monthly Archive Check

Scan {MEMORYCORE_PATH}/diary/current/ for files from previous months
For each file where month != current month:
- Create {MEMORYCORE_PATH}/diary/archived/YYYY-MM/ folder if not exists
- Move the file from current/ to archived/YYYY-MM/
Continue with diary write

Step 2: Find or Create Today's File

Check if {MEMORYCORE_PATH}/diary/current/YYYY-MM-DD.md exists
If exists: use it (will append new entry)
If not: create new file with header:

# YYYY-MM-DD — Session N: Brief Description

Step 3: Compose and Append Diary Entry

Get current date via bash: date +"%B %d, %Y" or PowerShell Get-Date -Format "MMMM dd, yyyy"
Analyze current session for key content
Write structured entry using our actual diary format:
- Title: # YYYY-MM-DD — Session N: Brief Description
- What Happened: Concise summary of the session context and goals
- Fixes Applied / Key Changes: Specific technical work done (commits, code changes)
- Key Insight: Lessons learned or important observations
- Pending / Next Steps: What's left to do
Session numbering: Read the existing file first. Find the highest Session N number in today's entries and increment by 1. If this is the first entry of the day, check the previous day's file for the last session number and continue from there. If no previous entries exist, start at Session 1.
APPEND to today's file (never overwrite existing content)
Multiple entries per day are separated by ---

Step 4: Update Session Memory

Update {MEMORYCORE_PATH}/core/session.md with:
- Session recap and key achievements
- Current working state for continuity
- Next steps identified
Confirm diary entry saved

Mandatory Rules

Always APPEND — never overwrite existing diary entries
One file per day — multiple entries separated by ---
Use real timestamps — get current date via system command
Archive first — run monthly archive check before every write
Evidence-based — document actual session content, not generic summaries
Use our format — concise technical summaries (What Happened, Key Changes, Key Insight, Pending)

Edge Cases

Situation	Behavior
First entry of the day	Create new file with header + first entry
Second+ entry same day	Append with `---` separator
No significant content	Create brief entry noting session type
"review diary" command	Read and present recent entries from current/

---name: save-diarydescription: MUST use when user says 'save diary', 'write diary', 'diary entry', 'update diary', or 'document session'. Also auto-trigger at the end of any significant session (feature shipped, major bug fixed, architecture decision, new project started).---# Dev Diary — Session Documentation Skill*Today's story takes shape.*## ActivationWhen this skill activates, output: "Dev Diary — documenting today's session."## Context Guard| Context | Status ||---------|--------|| User says "save diary" / "write diary" / "diary entry" | ACTIVE — full diary write || End of significant session | ACTIVE — auto-document || User says "review diary" | ACTIVE — read recent entries || Mid-conversation (no save request) | DORMANT — no diary action |## Protocol### Step 1: Monthly Archive Check- Scan `{MEMORYCORE_PATH}/diary/current/` for files from previous months- For each file where month != current month: - Create `{MEMORYCORE_PATH}/diary/archived/YYYY-MM/` folder if not exists - Move the file from `current/` to `archived/YYYY-MM/`- Continue with diary write### Step 2: Find or Create Today's File- Check if `{MEMORYCORE_PATH}/diary/current/YYYY-MM-DD.md` exists- If exists: use it (will append new entry)- If not: create new file with header:```# YYYY-MM-DD — Session N: Brief Description```### Step 3: Compose and Append Diary Entry- Get current date via bash: `date +"%B %d, %Y"` or PowerShell `Get-Date -Format "MMMM dd, yyyy"`- Analyze current session for key content- Write structured entry using our actual diary format: - **Title**: `# YYYY-MM-DD — Session N: Brief Description` - **What Happened**: Concise summary of the session context and goals - **Fixes Applied / Key Changes**: Specific technical work done (commits, code changes) - **Key Insight**: Lessons learned or important observations - **Pending / Next Steps**: What's left to do- **Session numbering**: Read the existing file first. Find the highest `Session N` number in today's entries and increment by 1. If this is the first entry of the day, check the previous day's file for the last session number and continue from there. If no previous entries exist, start at Session 1.- **APPEND** to today's file (never overwrite existing content)- Multiple entries per day are separated by `---`### Step 4: Update Session Memory- Update `{MEMORYCORE_PATH}/core/session.md` with: - Session recap and key achievements - Current working state for continuity - Next steps identified- Confirm diary entry saved## Mandatory Rules1. **Always APPEND** — never overwrite existing diary entries2. **One file per day** — multiple entries separated by `---`3. **Use real timestamps** — get current date via system command4. **Archive first** — run monthly archive check before every write5. **Evidence-based** — document actual session content, not generic summaries6. **Use our format** — concise technical summaries (What Happened, Key Changes, Key Insight, Pending)## Edge Cases| Situation | Behavior ||-----------|----------|| First entry of the day | Create new file with header + first entry || Second+ entry same day | Append with `---` separator || No significant content | Create brief entry noting session type || "review diary" command | Read and present recent entries from current/ |

Frequently asked questions